Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 748cfda7971edd609bbf9e5615dedacfb879bd593b4ce5d0f253688a5fd05fef

Tx prefix hash: 2f6a2573de46479c4412fe27808bd27eebf6f7c519055c695f0adbb5c3afcac5
Tx public key: ab9d013c5083e524d0f597e078991cc8013983afcaf2b8ede5acd0a35f9fe2d9
Timestamp: 1702779402 Timestamp [UCT]: 2023-12-17 02:16:42 Age [y:d:h:m:s]: 01:337:00:55:09
Block: 914786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499749 RingCT/type: yes/0
Extra: 01ab9d013c5083e524d0f597e078991cc8013983afcaf2b8ede5acd0a35f9fe2d902110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5737f109c639c3a748568c5cb34fe352701c0de3b206a9f84fc9261d7f70b186 0.600000000000 1372138 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": 914796, "vin": [ { "gen": { "height": 914786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5737f109c639c3a748568c5cb34fe352701c0de3b206a9f84fc9261d7f70b186" } } ], "extra": [ 1, 171, 157, 1, 60, 80, 131, 229, 36, 208, 245, 151, 224, 120, 153, 28, 200, 1, 57, 131, 175, 202, 242, 184, 237, 229, 172, 208, 163, 95, 159, 226, 217, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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