Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a50ac59595179e9182e95aa1327886b41ef4d272aeda0049a5457ab126f986aa

Tx prefix hash: e0530f9d27dfd7ece94977e7fb7d65ccc51091551a803a16fe980ea18b1d86af
Tx public key: 5f33be5bd9c1606676db23996fc1b3d3e1718de988a0a7e3d65b5dfe76efbcb6
Timestamp: 1708951909 Timestamp [UCT]: 2024-02-26 12:51:49 Age [y:d:h:m:s]: 01:025:06:24:13
Block: 965969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279066 RingCT/type: yes/0
Extra: 015f33be5bd9c1606676db23996fc1b3d3e1718de988a0a7e3d65b5dfe76efbcb60211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f9ea172a7e08f6fb7540b8ed990ddf71cade8c35de26d5828fa15461124c4bb 0.600000000000 1425724 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": 965979, "vin": [ { "gen": { "height": 965969 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f9ea172a7e08f6fb7540b8ed990ddf71cade8c35de26d5828fa15461124c4bb" } } ], "extra": [ 1, 95, 51, 190, 91, 217, 193, 96, 102, 118, 219, 35, 153, 111, 193, 179, 211, 225, 113, 141, 233, 136, 160, 167, 227, 214, 91, 93, 254, 118, 239, 188, 182, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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