Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6def293e4de32af9b06f558d676b709dbb4b3994fe928bc93757ac3a202f26cf

Tx prefix hash: 70d866d3e546313f75e357c2652ec680fd16cb84aa69abdc90786e0835fd327d
Tx public key: 8d903d74b5e0d9687e91c4732d34fafb57e5f4d406b3c1b577b5c584bf8f548c
Timestamp: 1653318186 Timestamp [UCT]: 2022-05-23 15:03:06 Age [y:d:h:m:s]: 03:161:11:23:48
Block: 507229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 894399 RingCT/type: yes/0
Extra: 018d903d74b5e0d9687e91c4732d34fafb57e5f4d406b3c1b577b5c584bf8f548c02110000000afaf35c9c000000000000000000

1 output(s) for total of 12.803831707000 dcy

stealth address amount amount idx
00: 5ffb6e60d4a2a21dad9d44c1ca9f86c73d7b4b41339611f0af3855aa785d3657 12.803831707000 932942 of 0

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": 507239, "vin": [ { "gen": { "height": 507229 } } ], "vout": [ { "amount": 12803831707, "target": { "key": "5ffb6e60d4a2a21dad9d44c1ca9f86c73d7b4b41339611f0af3855aa785d3657" } } ], "extra": [ 1, 141, 144, 61, 116, 181, 224, 217, 104, 126, 145, 196, 115, 45, 52, 250, 251, 87, 229, 244, 212, 6, 179, 193, 181, 119, 181, 197, 132, 191, 143, 84, 140, 2, 17, 0, 0, 0, 10, 250, 243, 92, 156, 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