Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ca2070d810cad65ff3268322e17c1e3b66bcf6099253e0e7c00040b49dc0f5

Tx prefix hash: e5c7bfeaad18f6481129dc605fc479617e12419f92814c56a89e43f515c5f899
Tx public key: 73433d8f10f4a0d3cc774c03081ac12abf2646eeaf1ad5a57a0e133c5a3c12de
Timestamp: 1722539220 Timestamp [UCT]: 2024-08-01 19:07:00 Age [y:d:h:m:s]: 00:241:20:47:44
Block: 1078596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172769 RingCT/type: yes/0
Extra: 0173433d8f10f4a0d3cc774c03081ac12abf2646eeaf1ad5a57a0e133c5a3c12de02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f16c5b4194f86024c79bbe0d0cb0a6ad47dbf21b183d22d9293b18b0f80a8360 0.600000000000 1551197 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": 1078606, "vin": [ { "gen": { "height": 1078596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f16c5b4194f86024c79bbe0d0cb0a6ad47dbf21b183d22d9293b18b0f80a8360" } } ], "extra": [ 1, 115, 67, 61, 143, 16, 244, 160, 211, 204, 119, 76, 3, 8, 26, 193, 42, 191, 38, 70, 238, 175, 26, 213, 165, 122, 14, 19, 60, 90, 60, 18, 222, 2, 17, 0, 0, 0, 12, 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