Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3de2ab6dfda7eca966f780ef1cdc3828059c2d1491d87e0af3f72316732ba9f2

Tx prefix hash: c3ea32fa37f62bf5c5ae0ec1158c701daf919966cbec1445ede5f4834312316a
Tx public key: 3d71ca86ea46fbde0e01ac2b22a58e373da10a8218a24ea4625693ae44a3373b
Timestamp: 1749297869 Timestamp [UCT]: 2025-06-07 12:04:29 Age [y:d:h:m:s]: 00:235:20:32:02
Block: 1299902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166168 RingCT/type: yes/0
Extra: 013d71ca86ea46fbde0e01ac2b22a58e373da10a8218a24ea4625693ae44a3373b02110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5481eeb7d2207dc3596aa37541d540b4c4c7ff37a69a77cb6b3acb52d6930d50 0.600000000000 1787445 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": 1299912, "vin": [ { "gen": { "height": 1299902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5481eeb7d2207dc3596aa37541d540b4c4c7ff37a69a77cb6b3acb52d6930d50" } } ], "extra": [ 1, 61, 113, 202, 134, 234, 70, 251, 222, 14, 1, 172, 43, 34, 165, 142, 55, 61, 161, 10, 130, 24, 162, 78, 164, 98, 86, 147, 174, 68, 163, 55, 59, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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