Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4988b8f75e5cfc4808179f36f32936aa5edcb06ecf0980b2578e8fc92331218

Tx prefix hash: 2ab5228dcb5e607d5e350454220294b79f37f5a63dcabde4f3f75c48a29624aa
Tx public key: a6586cb1abef0acc82c64775a4e8f14cb3b79ad39559494c0e596834a1efcd15
Timestamp: 1577534379 Timestamp [UCT]: 2019-12-28 11:59:39 Age [y:d:h:m:s]: 05:044:03:36:40
Block: 33451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1181431 RingCT/type: yes/0
Extra: 01a6586cb1abef0acc82c64775a4e8f14cb3b79ad39559494c0e596834a1efcd150211000000034ac5aa02000000000000000000

1 output(s) for total of 475.514547647000 dcy

stealth address amount amount idx
00: 1966be7e2ebe40440a952bab3b9ce679b8587b502b976465854fc779514e6692 475.514547647000 56014 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": 33461, "vin": [ { "gen": { "height": 33451 } } ], "vout": [ { "amount": 475514547647, "target": { "key": "1966be7e2ebe40440a952bab3b9ce679b8587b502b976465854fc779514e6692" } } ], "extra": [ 1, 166, 88, 108, 177, 171, 239, 10, 204, 130, 198, 71, 117, 164, 232, 241, 76, 179, 183, 154, 211, 149, 89, 73, 76, 14, 89, 104, 52, 161, 239, 205, 21, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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