Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0025cf3f6fb702ffcab840e960451751ae964fba67055adba6189b31600b4cac

Tx prefix hash: 50687b743736cc350a3f3ecfa0819ab6f03e087bcfdd3c80cc921b1af87b766f
Tx public key: e92fa2c546fe5f1a5efb1f0b8de9ee0cbd413c776902cafb2a6b38b25720f3e1
Timestamp: 1765787915 Timestamp [UCT]: 2025-12-15 08:38:35 Age [y:d:h:m:s]: 00:024:12:05:58
Block: 1434020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17558 RingCT/type: yes/0
Extra: 01e92fa2c546fe5f1a5efb1f0b8de9ee0cbd413c776902cafb2a6b38b25720f3e102110000000c70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 399340ba74115665bf0781ddb1f476d288dfef4f4b3afa4a65124d2e7345f5a8 0.600000000000 1922801 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": 1434030, "vin": [ { "gen": { "height": 1434020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "399340ba74115665bf0781ddb1f476d288dfef4f4b3afa4a65124d2e7345f5a8" } } ], "extra": [ 1, 233, 47, 162, 197, 70, 254, 95, 26, 94, 251, 31, 11, 141, 233, 238, 12, 189, 65, 60, 119, 105, 2, 202, 251, 42, 107, 56, 178, 87, 32, 243, 225, 2, 17, 0, 0, 0, 12, 112, 96, 157, 3, 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