Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ced7b9b7db246792a66ac87ef7bf9cab822e5f9aa6a2a6504274b005142e1f0

Tx prefix hash: 4706d4625a59470d11bd6c261a391846a7a513af3b6460e94b0b4f5d5f13cf67
Tx public key: af47b8d0e5e4d52df7ce001b3231690b26f94451e954768d6e1c176f34740384
Timestamp: 1731938110 Timestamp [UCT]: 2024-11-18 13:55:10 Age [y:d:h:m:s]: 00:199:07:06:24
Block: 1156427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142302 RingCT/type: yes/0
Extra: 01af47b8d0e5e4d52df7ce001b3231690b26f94451e954768d6e1c176f34740384021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22054e09279d9117a8ff4fe170293c0836c27e8c3b16f325dcc9fc6d11d70216 0.600000000000 1642050 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": 1156437, "vin": [ { "gen": { "height": 1156427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22054e09279d9117a8ff4fe170293c0836c27e8c3b16f325dcc9fc6d11d70216" } } ], "extra": [ 1, 175, 71, 184, 208, 229, 228, 213, 45, 247, 206, 0, 27, 50, 49, 105, 11, 38, 249, 68, 81, 233, 84, 118, 141, 110, 28, 23, 111, 52, 116, 3, 132, 2, 17, 0, 0, 0, 2, 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