Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaa1bca58a8ce03b595f683c7c3336ea29559b3723db465b71e25dc9ae3c50a1

Tx prefix hash: 9a5b956055b2e2f9c7d4aed09611700b4327533bcdb950b495d622920c2a04d6
Tx public key: f8e4b31f25f98a94045a848bd4e984a078c32ee88842eca1aa12a5920af4f87d
Timestamp: 1720693383 Timestamp [UCT]: 2024-07-11 10:23:03 Age [y:d:h:m:s]: 00:290:16:04:11
Block: 1063316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207677 RingCT/type: yes/0
Extra: 01f8e4b31f25f98a94045a848bd4e984a078c32ee88842eca1aa12a5920af4f87d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1227f54a0bf46bfdb3eb14017efe9bba5e596921135a022fe3907a48436698bf 0.600000000000 1533831 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": 1063326, "vin": [ { "gen": { "height": 1063316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1227f54a0bf46bfdb3eb14017efe9bba5e596921135a022fe3907a48436698bf" } } ], "extra": [ 1, 248, 228, 179, 31, 37, 249, 138, 148, 4, 90, 132, 139, 212, 233, 132, 160, 120, 195, 46, 232, 136, 66, 236, 161, 170, 18, 165, 146, 10, 244, 248, 125, 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