Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43d353c84aab79c8e596740cc7ee417f5fe8588530147f024f595a3491092f5

Tx prefix hash: 367d7aaec5b8c36a630b0bb5f65d91397af4e11278c47e83326eacdec826c989
Tx public key: fb6a94bef81b031c9edce2b4d9fe29c706af6b9dfdf0809ec8ce20d20ca84e15
Timestamp: 1626060020 Timestamp [UCT]: 2021-07-12 03:20:20 Age [y:d:h:m:s]: 03:167:16:32:27
Block: 292228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 890868 RingCT/type: yes/0
Extra: 01fb6a94bef81b031c9edce2b4d9fe29c706af6b9dfdf0809ec8ce20d20ca84e1502110000006a3634f08d000000000000000000

1 output(s) for total of 66.027952208000 dcy

stealth address amount amount idx
00: 44f3b8fc013fb28e9b6cfdd0fb47d3180c49adba9082065de649bbcb4f28277d 66.027952208000 612384 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": 292238, "vin": [ { "gen": { "height": 292228 } } ], "vout": [ { "amount": 66027952208, "target": { "key": "44f3b8fc013fb28e9b6cfdd0fb47d3180c49adba9082065de649bbcb4f28277d" } } ], "extra": [ 1, 251, 106, 148, 190, 248, 27, 3, 28, 158, 220, 226, 180, 217, 254, 41, 199, 6, 175, 107, 157, 253, 240, 128, 158, 200, 206, 32, 210, 12, 168, 78, 21, 2, 17, 0, 0, 0, 106, 54, 52, 240, 141, 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