Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1ede6201d7297843cacd73d92b871282a6f6a4211c1db690c5b1758e366c1d5

Tx prefix hash: 502ab8d1b64233737c03868fd12b56ef75a85ca3a60d86441243e2f58b5d8e55
Tx public key: 34b8b551596798faa8fbc400b0e33999f6dc1426fc3815ef3f1f407c78b186d4
Timestamp: 1748945227 Timestamp [UCT]: 2025-06-03 10:07:07 Age [y:d:h:m:s]: 00:169:17:26:30
Block: 1296986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118989 RingCT/type: yes/0
Extra: 0134b8b551596798faa8fbc400b0e33999f6dc1426fc3815ef3f1f407c78b186d4021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30a62393abd1eaafe1ffac83584d1b0951d4abec3f4b8e87db967042bb30676 0.600000000000 1784503 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": 1296996, "vin": [ { "gen": { "height": 1296986 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30a62393abd1eaafe1ffac83584d1b0951d4abec3f4b8e87db967042bb30676" } } ], "extra": [ 1, 52, 184, 181, 81, 89, 103, 152, 250, 168, 251, 196, 0, 176, 227, 57, 153, 246, 220, 20, 38, 252, 56, 21, 239, 63, 31, 64, 124, 120, 177, 134, 212, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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