Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc753c8d61b1e8257d94e519af6f1865759482253698861ad335b8a78f5f1f9

Tx prefix hash: e81c100bf6a4f371c1e9dc053267f66251ea933d114eff2566c8a6e2cd040b9b
Tx public key: 6082f035b92ec4e083868e7d2eafc0195ecc338151282484e050f3bc440c4797
Timestamp: 1746760115 Timestamp [UCT]: 2025-05-09 03:08:35 Age [y:d:h:m:s]: 00:196:12:47:50
Block: 1278872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138171 RingCT/type: yes/0
Extra: 016082f035b92ec4e083868e7d2eafc0195ecc338151282484e050f3bc440c4797021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548d3d56c0e3eae7c81248fef79b4a66c43b31b7f07d55db8603c173b019371f 0.600000000000 1766243 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": 1278882, "vin": [ { "gen": { "height": 1278872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548d3d56c0e3eae7c81248fef79b4a66c43b31b7f07d55db8603c173b019371f" } } ], "extra": [ 1, 96, 130, 240, 53, 185, 46, 196, 224, 131, 134, 142, 125, 46, 175, 192, 25, 94, 204, 51, 129, 81, 40, 36, 132, 224, 80, 243, 188, 68, 12, 71, 151, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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