Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef3dd82be7271f5260f3fd126bd05f68b79274a191f762d2a1b775ae0b6f398

Tx prefix hash: 28e70311274381608b5cbc8bbacf392be44b07f8431d6b918de49ae2e00309d7
Tx public key: a5cd232df0cac6b98f3615571df71fba35a1ab67d2b651b904c37446a635b426
Timestamp: 1732326252 Timestamp [UCT]: 2024-11-23 01:44:12 Age [y:d:h:m:s]: 00:001:08:41:25
Block: 1159653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 967 RingCT/type: yes/0
Extra: 01a5cd232df0cac6b98f3615571df71fba35a1ab67d2b651b904c37446a635b426021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc8fd3a0e01231a6096e618acaea6a904e525e95d7fb442a8abad7d6a38e8ee3 0.600000000000 1645292 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": 1159663, "vin": [ { "gen": { "height": 1159653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc8fd3a0e01231a6096e618acaea6a904e525e95d7fb442a8abad7d6a38e8ee3" } } ], "extra": [ 1, 165, 205, 35, 45, 240, 202, 198, 185, 143, 54, 21, 87, 29, 247, 31, 186, 53, 161, 171, 103, 210, 182, 81, 185, 4, 195, 116, 70, 166, 53, 180, 38, 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