Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d7ec6198c06678f6b9ccf3bc4a15cd0831ad5e125bf5eb2d9e377ab37cf9fc

Tx prefix hash: 910a48bf9ff93613de13439cfc8506026e0aa9ce85293016dbf26fd25e5895ee
Tx public key: f429fd340dd3ded2cc6e99354f9949d3d77d062a44ae884e8fa678427441d980
Timestamp: 1758891265 Timestamp [UCT]: 2025-09-26 12:54:25 Age [y:d:h:m:s]: 00:104:01:39:30
Block: 1376887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74508 RingCT/type: yes/0
Extra: 01f429fd340dd3ded2cc6e99354f9949d3d77d062a44ae884e8fa678427441d98002110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07c9b82f55ea7ec4fa49a5954cf4ec9eec9b27a3d7eee67f5fac0beb93c4070f 0.600000000000 1864978 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": 1376897, "vin": [ { "gen": { "height": 1376887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07c9b82f55ea7ec4fa49a5954cf4ec9eec9b27a3d7eee67f5fac0beb93c4070f" } } ], "extra": [ 1, 244, 41, 253, 52, 13, 211, 222, 210, 204, 110, 153, 53, 79, 153, 73, 211, 215, 125, 6, 42, 68, 174, 136, 78, 143, 166, 120, 66, 116, 65, 217, 128, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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