Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ea4365eb93c77abdca7b6ddab70c4a6e33db79851410eabac4ded7c2d8f32d6

Tx prefix hash: 466f6ba9753f1c328e3895eab58698ea74ba22263838e34ac3779913a44e3b93
Tx public key: df0f0c9222f85281f386e2659f47cdb7dcf08377a4bfb2c7548e726251efcbdf
Timestamp: 1725060151 Timestamp [UCT]: 2024-08-30 23:22:31 Age [y:d:h:m:s]: 00:123:15:37:32
Block: 1099503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88443 RingCT/type: yes/0
Extra: 01df0f0c9222f85281f386e2659f47cdb7dcf08377a4bfb2c7548e726251efcbdf021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3469d386b8e8676cecb8bb526c8abde37daa1de986c8d071730d611fca175065 0.600000000000 1575466 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": 1099513, "vin": [ { "gen": { "height": 1099503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3469d386b8e8676cecb8bb526c8abde37daa1de986c8d071730d611fca175065" } } ], "extra": [ 1, 223, 15, 12, 146, 34, 248, 82, 129, 243, 134, 226, 101, 159, 71, 205, 183, 220, 240, 131, 119, 164, 191, 178, 199, 84, 142, 114, 98, 81, 239, 203, 223, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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