Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c1a24d24322a5217d1438349ba227999e469a5fb5e39453d83a26c87e14e5f

Tx prefix hash: 99d14534562a7f321f46a2662f915fa86c7e200cc5242529567c7b3895438a70
Tx public key: ba34f2d6a61090b06d08191cafc25e1ff658ac6f19882af8b0d886c8a3f8b70f
Timestamp: 1734792570 Timestamp [UCT]: 2024-12-21 14:49:30 Age [y:d:h:m:s]: 00:093:06:50:43
Block: 1180103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66419 RingCT/type: yes/0
Extra: 01ba34f2d6a61090b06d08191cafc25e1ff658ac6f19882af8b0d886c8a3f8b70f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b128cedaa94bb1b32bf0d40e89ef7313e5469af06f40c611e87b2ba1198e22d2 0.600000000000 1666508 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": 1180113, "vin": [ { "gen": { "height": 1180103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b128cedaa94bb1b32bf0d40e89ef7313e5469af06f40c611e87b2ba1198e22d2" } } ], "extra": [ 1, 186, 52, 242, 214, 166, 16, 144, 176, 109, 8, 25, 28, 175, 194, 94, 31, 246, 88, 172, 111, 25, 136, 42, 248, 176, 216, 134, 200, 163, 248, 183, 15, 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