Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f157c40caf193750de96c1de7dc2a0ab317c8e4486fe0c12a8cf26754982eef3

Tx prefix hash: a85848d42319590cc5a2d69b0fce2be84d3ffa2ca22328e50e4637bb3a2c15fc
Tx public key: f8f65ff8136227f5eae025f8d0ff2907515225c301ef416d7fc1c80c91ab424a
Timestamp: 1715617835 Timestamp [UCT]: 2024-05-13 16:30:35 Age [y:d:h:m:s]: 01:179:23:46:55
Block: 1021230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387253 RingCT/type: yes/0
Extra: 01f8f65ff8136227f5eae025f8d0ff2907515225c301ef416d7fc1c80c91ab424a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f739e63792d11306e597e980b1a63346dc0e90bbba5fb4ff9609ab9ae1c6cb5 0.600000000000 1485489 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": 1021240, "vin": [ { "gen": { "height": 1021230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f739e63792d11306e597e980b1a63346dc0e90bbba5fb4ff9609ab9ae1c6cb5" } } ], "extra": [ 1, 248, 246, 95, 248, 19, 98, 39, 245, 234, 224, 37, 248, 208, 255, 41, 7, 81, 82, 37, 195, 1, 239, 65, 109, 127, 193, 200, 12, 145, 171, 66, 74, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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