Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20323fedbdfcb5d872aba319f21562c91c967ea1c5a68c83ed7a4c77a3444d91

Tx prefix hash: 6388f380ae84159b5350dccb342515a2bd2e1a223ab6a0434c89df92221c6ab7
Tx public key: 38bda0b0f9924a4993f577c6bfafb994d3ff34bce4be7203bb471324a1d32acc
Timestamp: 1702268231 Timestamp [UCT]: 2023-12-11 04:17:11 Age [y:d:h:m:s]: 01:135:22:57:14
Block: 910550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358324 RingCT/type: yes/0
Extra: 0138bda0b0f9924a4993f577c6bfafb994d3ff34bce4be7203bb471324a1d32acc02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21da69f801d28eb73636cf0863dff90a97e7aed56f28626882a7b2c472490e92 0.600000000000 1367711 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": 910560, "vin": [ { "gen": { "height": 910550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21da69f801d28eb73636cf0863dff90a97e7aed56f28626882a7b2c472490e92" } } ], "extra": [ 1, 56, 189, 160, 176, 249, 146, 74, 73, 147, 245, 119, 198, 191, 175, 185, 148, 211, 255, 52, 188, 228, 190, 114, 3, 187, 71, 19, 36, 161, 211, 42, 204, 2, 17, 0, 0, 0, 6, 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