Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4afd65b8990ebaa7e60ffd57f6e3e0080c9651c40884538eebd13bf2b9e367e

Tx prefix hash: 625e448bf2bf533a830032405cf961a56d8f4003bb2285dcf6aa5a36a710eda3
Tx public key: a82082d720a98eb2019b23138ba33dead03e4829d5391bd0c9a6aea243cac7cf
Timestamp: 1726716374 Timestamp [UCT]: 2024-09-19 03:26:14 Age [y:d:h:m:s]: 00:198:11:33:46
Block: 1113229 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141684 RingCT/type: yes/0
Extra: 01a82082d720a98eb2019b23138ba33dead03e4829d5391bd0c9a6aea243cac7cf021100000002bdafe9cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7d58e40b346c800c4f432b27dcbe4e9d2ade511fe3822028ce6cd03b5bd0b9c 0.600000000000 1592830 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": 1113239, "vin": [ { "gen": { "height": 1113229 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7d58e40b346c800c4f432b27dcbe4e9d2ade511fe3822028ce6cd03b5bd0b9c" } } ], "extra": [ 1, 168, 32, 130, 215, 32, 169, 142, 178, 1, 155, 35, 19, 139, 163, 61, 234, 208, 62, 72, 41, 213, 57, 27, 208, 201, 166, 174, 162, 67, 202, 199, 207, 2, 17, 0, 0, 0, 2, 189, 175, 233, 204, 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