Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2719ff425b849aee6abfe857a179b6e7137147712c20018e09e0fbb2b9ae69d

Tx prefix hash: 70bdfd86504b2db6cec07fd56de7ec5a250282278525660f2d20ae216c8b6e03
Tx public key: 3b6e5fe18916dcb4dd1858ee9fc2459f5ed555ec8f5caa0f4f2692a0a8ec3d15
Timestamp: 1706643039 Timestamp [UCT]: 2024-01-30 19:30:39 Age [y:d:h:m:s]: 01:286:19:00:58
Block: 946798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 463777 RingCT/type: yes/0
Extra: 013b6e5fe18916dcb4dd1858ee9fc2459f5ed555ec8f5caa0f4f2692a0a8ec3d150211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0378def80ee437954c761bba3114ca40e7d5d7c488c4454663f7afde9a81297 0.600000000000 1405138 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": 946808, "vin": [ { "gen": { "height": 946798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0378def80ee437954c761bba3114ca40e7d5d7c488c4454663f7afde9a81297" } } ], "extra": [ 1, 59, 110, 95, 225, 137, 22, 220, 180, 221, 24, 88, 238, 159, 194, 69, 159, 94, 213, 85, 236, 143, 92, 170, 15, 79, 38, 146, 160, 168, 236, 61, 21, 2, 17, 0, 0, 0, 1, 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