Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c11824b2af3ba4fe48aeea15f4f67a57ada4ca3ce4f29edd5b04867295ca67c1

Tx prefix hash: b1284ce85c66101919096a89399a19c427a1b3859227f99401c83e123b9ed0d8
Tx public key: d1252b03cb6a23acc8dc1d4c7b93041168b00cad7139a18a42b84dd1a5486624
Timestamp: 1747161240 Timestamp [UCT]: 2025-05-13 18:34:00 Age [y:d:h:m:s]: 00:224:00:26:06
Block: 1282212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157836 RingCT/type: yes/0
Extra: 01d1252b03cb6a23acc8dc1d4c7b93041168b00cad7139a18a42b84dd1a54866240211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa0b068a789f1ee11f531624ffb123fff2e2d157408fc1a0e741305d94cfb35d 0.600000000000 1769619 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1282222, "vin": [ { "gen": { "height": 1282212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa0b068a789f1ee11f531624ffb123fff2e2d157408fc1a0e741305d94cfb35d" } } ], "extra": [ 1, 209, 37, 43, 3, 203, 106, 35, 172, 200, 220, 29, 76, 123, 147, 4, 17, 104, 176, 12, 173, 113, 57, 161, 138, 66, 184, 77, 209, 165, 72, 102, 36, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8