Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417b2055dad563e62f847bb3fe8fe5cb02a0edd29f1222e71368ddc50fe174df

Tx prefix hash: 1143336c2230d2978cfd5a42f440cb8f041601cf2007d3fcc9e731eb0daed937
Tx public key: 86084f2e891b012ce872159282b84ca72b7163587e23d3258f9ea16b7d4b680a
Timestamp: 1717949091 Timestamp [UCT]: 2024-06-09 16:04:51 Age [y:d:h:m:s]: 00:267:05:20:57
Block: 1040557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190944 RingCT/type: yes/0
Extra: 0186084f2e891b012ce872159282b84ca72b7163587e23d3258f9ea16b7d4b680a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ff849f911bd935c05b6edf17f248e1d2b5c420cc9aa55f9fd9894e4c8a9d533 0.600000000000 1509214 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": 1040567, "vin": [ { "gen": { "height": 1040557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ff849f911bd935c05b6edf17f248e1d2b5c420cc9aa55f9fd9894e4c8a9d533" } } ], "extra": [ 1, 134, 8, 79, 46, 137, 27, 1, 44, 232, 114, 21, 146, 130, 184, 76, 167, 43, 113, 99, 88, 126, 35, 211, 37, 143, 158, 161, 107, 125, 75, 104, 10, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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