Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9241e38f382151583d9183f96293d572fc635ffdf3ed74ae76f760308caf71

Tx prefix hash: 54cfc51b0ad66fc61a5b6b45b5b19c11d2b9f12cc8cafc04668a061db6a43739
Tx public key: e5c91c75e2d4ac8aaca14b32841e66d551d797209d8bececb50fa9e2a508d680
Timestamp: 1737757003 Timestamp [UCT]: 2025-01-24 22:16:43 Age [y:d:h:m:s]: 00:145:02:30:45
Block: 1204570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103438 RingCT/type: yes/0
Extra: 01e5c91c75e2d4ac8aaca14b32841e66d551d797209d8bececb50fa9e2a508d680021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 473148ac9ef63bb02a86f76b9bb3535259123f8d5809407d99022e5e9d619450 0.600000000000 1691259 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": 1204580, "vin": [ { "gen": { "height": 1204570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "473148ac9ef63bb02a86f76b9bb3535259123f8d5809407d99022e5e9d619450" } } ], "extra": [ 1, 229, 201, 28, 117, 226, 212, 172, 138, 172, 161, 75, 50, 132, 30, 102, 213, 81, 215, 151, 32, 157, 139, 236, 236, 181, 15, 169, 226, 165, 8, 214, 128, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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