Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1260892b8af44c778098a53e340a7b6ede7f2474425bab3ffd7238af7182f149

Tx prefix hash: ab4370b1f64006b9ea657559fd15e7f98d12cae705bddc38554c8ca3e7e10f57
Tx public key: e74bd7647d3461e88d55e8a13c1d2876d2484e05522fd511ec89e31600f5b8dd
Timestamp: 1730559029 Timestamp [UCT]: 2024-11-02 14:50:29 Age [y:d:h:m:s]: 00:212:13:28:04
Block: 1145006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151797 RingCT/type: yes/0
Extra: 01e74bd7647d3461e88d55e8a13c1d2876d2484e05522fd511ec89e31600f5b8dd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32f47c0a0f756a81dc42ee9a6d8f0b57b3b66db22dc18c60557dfb111b3fe549 0.600000000000 1629365 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": 1145016, "vin": [ { "gen": { "height": 1145006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32f47c0a0f756a81dc42ee9a6d8f0b57b3b66db22dc18c60557dfb111b3fe549" } } ], "extra": [ 1, 231, 75, 215, 100, 125, 52, 97, 232, 141, 85, 232, 161, 60, 29, 40, 118, 210, 72, 78, 5, 82, 47, 213, 17, 236, 137, 227, 22, 0, 245, 184, 221, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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