Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5431c6fb4f1b906b7520e7b96deec6c42a2f8a5df67a6f35855cc5b5c8724a98

Tx prefix hash: 943f1374ea2ec712fa61189c5049249f7472b7e049bd077f8c029c5cb13d9319
Tx public key: 3498660a0f39b934ce5fc5249fda7cfa0ac344dfb181b9359f0963fb64e9e5a9
Timestamp: 1702392533 Timestamp [UCT]: 2023-12-12 14:48:53 Age [y:d:h:m:s]: 01:125:22:51:26
Block: 911598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351145 RingCT/type: yes/0
Extra: 013498660a0f39b934ce5fc5249fda7cfa0ac344dfb181b9359f0963fb64e9e5a902110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0da1df6bd008ea43f5f1f5ad22472a14b6be911ca7fad9be3ef8752ada96745d 0.600000000000 1368812 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": 911608, "vin": [ { "gen": { "height": 911598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0da1df6bd008ea43f5f1f5ad22472a14b6be911ca7fad9be3ef8752ada96745d" } } ], "extra": [ 1, 52, 152, 102, 10, 15, 57, 185, 52, 206, 95, 197, 36, 159, 218, 124, 250, 10, 195, 68, 223, 177, 129, 185, 53, 159, 9, 99, 251, 100, 233, 229, 169, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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