Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0e9e6c0774a0326ddab568c14c46a387522a333f622d37172fc3909e0342eb5

Tx prefix hash: 8eec01ce4d5f2c3995f1599e92bbd4bbc1ffc3f9e44ecc289caec2f913f0334b
Tx public key: 323c47f9b4cfa0c580a56910bcf08b8fce232b4062cba23a63ddd7f8b698a201
Timestamp: 1718240965 Timestamp [UCT]: 2024-06-13 01:09:25 Age [y:d:h:m:s]: 00:277:11:41:56
Block: 1042981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198302 RingCT/type: yes/0
Extra: 01323c47f9b4cfa0c580a56910bcf08b8fce232b4062cba23a63ddd7f8b698a2010211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1389e863ad58dc2a9a293b7b51a8236800f110fe20826c77e400934ac946b661 0.600000000000 1512020 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": 1042991, "vin": [ { "gen": { "height": 1042981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1389e863ad58dc2a9a293b7b51a8236800f110fe20826c77e400934ac946b661" } } ], "extra": [ 1, 50, 60, 71, 249, 180, 207, 160, 197, 128, 165, 105, 16, 188, 240, 139, 143, 206, 35, 43, 64, 98, 203, 162, 58, 99, 221, 215, 248, 182, 152, 162, 1, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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