Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77d86a80c8665bb752ca1a95f2131b936635d013fb3465639135659e8363ea5e

Tx prefix hash: 6ca1b69ce5bde599e612ab08dca36e51c6e3f41c225c03571cc9def49c27d31b
Tx public key: 0e1b36fd9936291d86ecfed3bf893446b930477fc2c4ba724d504f78757c64b7
Timestamp: 1751183744 Timestamp [UCT]: 2025-06-29 07:55:44 Age [y:d:h:m:s]: 00:144:00:27:19
Block: 1315063 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101051 RingCT/type: yes/0
Extra: 010e1b36fd9936291d86ecfed3bf893446b930477fc2c4ba724d504f78757c64b702110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c0405eada9e45bf87ec1d341fe2c20a01d3a43a57c742dcc3d1bc1158f01e8c 0.600000000000 1802716 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": 1315073, "vin": [ { "gen": { "height": 1315063 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c0405eada9e45bf87ec1d341fe2c20a01d3a43a57c742dcc3d1bc1158f01e8c" } } ], "extra": [ 1, 14, 27, 54, 253, 153, 54, 41, 29, 134, 236, 254, 211, 191, 137, 52, 70, 185, 48, 71, 127, 194, 196, 186, 114, 77, 80, 79, 120, 117, 124, 100, 183, 2, 17, 0, 0, 0, 3, 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