Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad7b7c30b45980cd9e3aafcdb7b0a91e12ae11127906a1f817590e63d91ae65f

Tx prefix hash: 537d94a7c83894859515a220459733272ca600fb6e1080f9b1621c31cf0b8f00
Tx public key: d694891c731445df2fc67c50c7eaeeeb9ccbf50bf1996c927d10b7ade51c9c4b
Timestamp: 1713313914 Timestamp [UCT]: 2024-04-17 00:31:54 Age [y:d:h:m:s]: 00:267:21:19:35
Block: 1002109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191769 RingCT/type: yes/0
Extra: 01d694891c731445df2fc67c50c7eaeeeb9ccbf50bf1996c927d10b7ade51c9c4b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9b08d4c960ce904cbc1b9874d6539baf66239e639d072a1c6ee84b64b781856 0.600000000000 1462625 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": 1002119, "vin": [ { "gen": { "height": 1002109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9b08d4c960ce904cbc1b9874d6539baf66239e639d072a1c6ee84b64b781856" } } ], "extra": [ 1, 214, 148, 137, 28, 115, 20, 69, 223, 47, 198, 124, 80, 199, 234, 238, 235, 156, 203, 245, 11, 241, 153, 108, 146, 125, 16, 183, 173, 229, 28, 156, 75, 2, 17, 0, 0, 0, 2, 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