Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13ac1d573da3a95fdfd382f0ee2b8b60e4fc214ec4fbb96ea9f622a40573ce76

Tx prefix hash: bf73854a7a4b18846fa4e12225e910ec4f9a7ac81ca65230f730f33fab7e012d
Tx public key: 447c672ef36d338b49d4eecbc53971e559e5590768d28da3f9ec9128caefa246
Timestamp: 1707835833 Timestamp [UCT]: 2024-02-13 14:50:33 Age [y:d:h:m:s]: 01:038:10:46:13
Block: 956704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288513 RingCT/type: yes/0
Extra: 01447c672ef36d338b49d4eecbc53971e559e5590768d28da3f9ec9128caefa24602110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a1043c2bec62a301d6c015af0697227c180e426ecb39d750c03fd4d1ec57f7a 0.600000000000 1416014 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": 956714, "vin": [ { "gen": { "height": 956704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a1043c2bec62a301d6c015af0697227c180e426ecb39d750c03fd4d1ec57f7a" } } ], "extra": [ 1, 68, 124, 103, 46, 243, 109, 51, 139, 73, 212, 238, 203, 197, 57, 113, 229, 89, 229, 89, 7, 104, 210, 141, 163, 249, 236, 145, 40, 202, 239, 162, 70, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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