Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4ab7fb78b94cc55cdb8658872bab7e79b78e6f273ba9b76a15fd8c5814ddba3

Tx prefix hash: ff86fe458749dda9e3c4eb0f7af0e52531b543c8435c2d65a83d9c775642b50e
Tx public key: 82cb1b55f60851ae7e2326e44e614b2903680c8a128e103a38ffe6be0217783f
Timestamp: 1702115207 Timestamp [UCT]: 2023-12-09 09:46:47 Age [y:d:h:m:s]: 01:113:13:10:23
Block: 909273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342300 RingCT/type: yes/0
Extra: 0182cb1b55f60851ae7e2326e44e614b2903680c8a128e103a38ffe6be0217783f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26c14b9f30f45bdfc7b476d90a763f250565d1f891db38a8e8fcff84f286b76d 0.600000000000 1366344 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": 909283, "vin": [ { "gen": { "height": 909273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26c14b9f30f45bdfc7b476d90a763f250565d1f891db38a8e8fcff84f286b76d" } } ], "extra": [ 1, 130, 203, 27, 85, 246, 8, 81, 174, 126, 35, 38, 228, 78, 97, 75, 41, 3, 104, 12, 138, 18, 142, 16, 58, 56, 255, 230, 190, 2, 23, 120, 63, 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