Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c3259d316be610c4b4ba72c15fb58fa10cce9f20376c3b2d492eb76dbcb5ca

Tx prefix hash: 4cc5d4772a59424f2d1c89e4cf703c2cea905f71c43ab8062cf2386266501ac6
Tx public key: 1c9eef8e935128113762ec01e12906f84b90d37dfd5a828f7a885543dacc33b5
Timestamp: 1712339472 Timestamp [UCT]: 2024-04-05 17:51:12 Age [y:d:h:m:s]: 01:002:07:57:18
Block: 994008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262642 RingCT/type: yes/0
Extra: 011c9eef8e935128113762ec01e12906f84b90d37dfd5a828f7a885543dacc33b502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29ac1cf9879bb12d19163960b3db936ea7b80f631df25f99c451d0d1a2ad42cb 0.600000000000 1454404 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": 994018, "vin": [ { "gen": { "height": 994008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29ac1cf9879bb12d19163960b3db936ea7b80f631df25f99c451d0d1a2ad42cb" } } ], "extra": [ 1, 28, 158, 239, 142, 147, 81, 40, 17, 55, 98, 236, 1, 225, 41, 6, 248, 75, 144, 211, 125, 253, 90, 130, 143, 122, 136, 85, 67, 218, 204, 51, 181, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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