Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 635d4ea38b62431487e4197a41b04b08b8774c35897123808788fc6d26938ca4

Tx prefix hash: 301bb8ccfcd7dcdee4e1517c266d84d8e8bb313ecef29c770cb24b6d35bb064e
Tx public key: b4f3e1c555c324d140ebf719dfe3a44b361fb37942e3fbda3eca5a247fcb1760
Timestamp: 1704114646 Timestamp [UCT]: 2024-01-01 13:10:46 Age [y:d:h:m:s]: 01:313:00:49:35
Block: 925845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482568 RingCT/type: yes/0
Extra: 01b4f3e1c555c324d140ebf719dfe3a44b361fb37942e3fbda3eca5a247fcb176002110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4769345c971c8c125625128313a5c570b46dca7e9fa67379e686c7febe62ae5 0.600000000000 1383615 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": 925855, "vin": [ { "gen": { "height": 925845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4769345c971c8c125625128313a5c570b46dca7e9fa67379e686c7febe62ae5" } } ], "extra": [ 1, 180, 243, 225, 197, 85, 195, 36, 209, 64, 235, 247, 25, 223, 227, 164, 75, 54, 31, 179, 121, 66, 227, 251, 218, 62, 202, 90, 36, 127, 203, 23, 96, 2, 17, 0, 0, 0, 5, 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