Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71b32aa1f3cc0ab0c9904b38374672f605a07356e240b6192c395da9df2e7ed3

Tx prefix hash: dd2dc3709247f5306a7fc9715019e526ad65475c6e7c20341390a95164757b96
Tx public key: f9adf9f0242a40b3fe881f73c868ff7d3e56a4f97bc6037ddf4318cfa61322b3
Timestamp: 1702886778 Timestamp [UCT]: 2023-12-18 08:06:18 Age [y:d:h:m:s]: 01:188:03:40:57
Block: 915681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395437 RingCT/type: yes/0
Extra: 01f9adf9f0242a40b3fe881f73c868ff7d3e56a4f97bc6037ddf4318cfa61322b302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b0d491f170cf15d9be11ebebca186dc64cee115e90a9983b5c52e61325e81a 0.600000000000 1373091 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": 915691, "vin": [ { "gen": { "height": 915681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b0d491f170cf15d9be11ebebca186dc64cee115e90a9983b5c52e61325e81a" } } ], "extra": [ 1, 249, 173, 249, 240, 36, 42, 64, 179, 254, 136, 31, 115, 200, 104, 255, 125, 62, 86, 164, 249, 123, 198, 3, 125, 223, 67, 24, 207, 166, 19, 34, 179, 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