Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e741094f2dbc39c6cc716533213cc3297e887336893e6cb889ad6914c0f5dc

Tx prefix hash: 544b34ae9e2bc9f3d47029495a76232dc8ab043e62b02e69033b875f1d004f9b
Tx public key: ad588ddcfa17dae88c38dc0355c54c3227729fd35e8ed2d7a54aa1ffcb633181
Timestamp: 1735377412 Timestamp [UCT]: 2024-12-28 09:16:52 Age [y:d:h:m:s]: 00:102:19:14:59
Block: 1184910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73266 RingCT/type: yes/0
Extra: 01ad588ddcfa17dae88c38dc0355c54c3227729fd35e8ed2d7a54aa1ffcb633181021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166f2fcb8ae69c4ac38637653d99090315f333c111576002c702be88867fa2f3 0.600000000000 1671373 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": 1184920, "vin": [ { "gen": { "height": 1184910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166f2fcb8ae69c4ac38637653d99090315f333c111576002c702be88867fa2f3" } } ], "extra": [ 1, 173, 88, 141, 220, 250, 23, 218, 232, 140, 56, 220, 3, 85, 197, 76, 50, 39, 114, 159, 211, 94, 142, 210, 215, 165, 74, 161, 255, 203, 99, 49, 129, 2, 17, 0, 0, 0, 7, 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