Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6296ca907f0428745735fe0c8b43ec401f16d04dd7024abe7f04c7d43d5c8683

Tx prefix hash: 2ca05d18db228d5a70a2cefddcad58b02daeb982684972b811bfd0b585973666
Tx public key: 4df6c50f48ee934a85a7d93cc717ef39ea3fff231283787ac4df408922f1dff1
Timestamp: 1722873313 Timestamp [UCT]: 2024-08-05 15:55:13 Age [y:d:h:m:s]: 00:201:00:00:38
Block: 1081370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143506 RingCT/type: yes/0
Extra: 014df6c50f48ee934a85a7d93cc717ef39ea3fff231283787ac4df408922f1dff1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 219632cf5b83af3af7b1cac732c1ba53952928a6dbc9614fee0f456b545ccf9f 0.600000000000 1555089 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": 1081380, "vin": [ { "gen": { "height": 1081370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "219632cf5b83af3af7b1cac732c1ba53952928a6dbc9614fee0f456b545ccf9f" } } ], "extra": [ 1, 77, 246, 197, 15, 72, 238, 147, 74, 133, 167, 217, 60, 199, 23, 239, 57, 234, 63, 255, 35, 18, 131, 120, 122, 196, 223, 64, 137, 34, 241, 223, 241, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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