Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6351adcb929ee8736ecde09270309400107ef4651962c3b3d4bbec7dc597e9f9

Tx prefix hash: 99a722f930dde806b4c3a214e47cb474c66fe50e76146f4df89548058d00673e
Tx public key: e985700e1e4183a1f02b3cc5ced8ed19c28dd0694abc2ae3b2f464f040e252bf
Timestamp: 1732250596 Timestamp [UCT]: 2024-11-22 04:43:16 Age [y:d:h:m:s]: 00:122:17:21:21
Block: 1159017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87518 RingCT/type: yes/0
Extra: 01e985700e1e4183a1f02b3cc5ced8ed19c28dd0694abc2ae3b2f464f040e252bf021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc805ec9053b2277d52411ac05a0041a7fde98c96d02c3c9e83fadddcb9f7e7d 0.600000000000 1644648 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": 1159027, "vin": [ { "gen": { "height": 1159017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc805ec9053b2277d52411ac05a0041a7fde98c96d02c3c9e83fadddcb9f7e7d" } } ], "extra": [ 1, 233, 133, 112, 14, 30, 65, 131, 161, 240, 43, 60, 197, 206, 216, 237, 25, 194, 141, 208, 105, 74, 188, 42, 227, 178, 244, 100, 240, 64, 226, 82, 191, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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