Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4fb2429e27929e103308bc154bf2ad4640f3f46f78fdf3f2bdca701f295651a3

Tx prefix hash: 17e10f0b0d73fae191555d956cf2db410d4402e1b80d63c4e3e0d4421ad633f9
Tx public key: 177f52e9ab4dba71d9106d4d8fbf96004c43bc18a3097f3da5c7515adc6715f7
Timestamp: 1735793579 Timestamp [UCT]: 2025-01-02 04:52:59 Age [y:d:h:m:s]: 00:167:12:04:32
Block: 1188356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119430 RingCT/type: yes/0
Extra: 01177f52e9ab4dba71d9106d4d8fbf96004c43bc18a3097f3da5c7515adc6715f7021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef54e6538f46a04ec164077fe065bd1de1d08b8552506e5b81092e0f85e320b0 0.600000000000 1674857 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": 1188366, "vin": [ { "gen": { "height": 1188356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef54e6538f46a04ec164077fe065bd1de1d08b8552506e5b81092e0f85e320b0" } } ], "extra": [ 1, 23, 127, 82, 233, 171, 77, 186, 113, 217, 16, 109, 77, 143, 191, 150, 0, 76, 67, 188, 24, 163, 9, 127, 61, 165, 199, 81, 90, 220, 103, 21, 247, 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