Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3fda59ace77e1cae1a2c258c7c738159ccfc2447914e88c89a396fe80f910dc

Tx prefix hash: ec294b1ec5ce3e13939376bc6cd53c26956f9f3a18b3e175821b17876547e478
Tx public key: 57960407c29e10c197af63f6c238df36c89cec264e1de51a07d798117542d54e
Timestamp: 1722474460 Timestamp [UCT]: 2024-08-01 01:07:40 Age [y:d:h:m:s]: 00:175:08:36:58
Block: 1078065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125412 RingCT/type: yes/0
Extra: 0157960407c29e10c197af63f6c238df36c89cec264e1de51a07d798117542d54e021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fc5e9b56840508fda8cfe4d5590f4da36cedd2aaf2b3c68b41f3b9156f3eae6 0.600000000000 1550622 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": 1078075, "vin": [ { "gen": { "height": 1078065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fc5e9b56840508fda8cfe4d5590f4da36cedd2aaf2b3c68b41f3b9156f3eae6" } } ], "extra": [ 1, 87, 150, 4, 7, 194, 158, 16, 193, 151, 175, 99, 246, 194, 56, 223, 54, 200, 156, 236, 38, 78, 29, 229, 26, 7, 215, 152, 17, 117, 66, 213, 78, 2, 17, 0, 0, 0, 8, 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