Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3f30bdedb5b2ee787c4c0ff6b90d544667509c6102ea0b545498bbd5074e8cb

Tx prefix hash: a8ad45388bb412d0a0ae6a2998f4afdeae954bb5b5423e3e0bde0091c4cb752c
Tx public key: c27029361de97d0c6dba29f1b242d9c2760e533b13ca7277ab84c62d92444443
Timestamp: 1732233156 Timestamp [UCT]: 2024-11-21 23:52:36 Age [y:d:h:m:s]: 00:144:06:00:05
Block: 1158882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102911 RingCT/type: yes/0
Extra: 01c27029361de97d0c6dba29f1b242d9c2760e533b13ca7277ab84c62d92444443021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3704d0eeb4acf1c04d0b85c743a5562090efc87817498a22a6100ac708188c32 0.600000000000 1644513 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": 1158892, "vin": [ { "gen": { "height": 1158882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3704d0eeb4acf1c04d0b85c743a5562090efc87817498a22a6100ac708188c32" } } ], "extra": [ 1, 194, 112, 41, 54, 29, 233, 125, 12, 109, 186, 41, 241, 178, 66, 217, 194, 118, 14, 83, 59, 19, 202, 114, 119, 171, 132, 198, 45, 146, 68, 68, 67, 2, 17, 0, 0, 0, 4, 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