Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 460042d62b4e3eb1c43fc58d38958dbaf9f30fc66f37e9a30f4a5371b300b0f6

Tx prefix hash: d92264a71613eb4374f2e036ccc14d12f54a66c59444605c19d82a8d531f669f
Tx public key: 5baa32f2ae36117ca93fd423d4e24cceef750dd5fb56dc6fee50757820542a46
Timestamp: 1716150959 Timestamp [UCT]: 2024-05-19 20:35:59 Age [y:d:h:m:s]: 00:330:12:40:02
Block: 1025644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236254 RingCT/type: yes/0
Extra: 015baa32f2ae36117ca93fd423d4e24cceef750dd5fb56dc6fee50757820542a460211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4648622fad9b762b9a75f620932ca5ba8fd63ebc02f16a4ad2f1e8677ac2722c 0.600000000000 1492295 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": 1025654, "vin": [ { "gen": { "height": 1025644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4648622fad9b762b9a75f620932ca5ba8fd63ebc02f16a4ad2f1e8677ac2722c" } } ], "extra": [ 1, 91, 170, 50, 242, 174, 54, 17, 124, 169, 63, 212, 35, 212, 226, 76, 206, 239, 117, 13, 213, 251, 86, 220, 111, 238, 80, 117, 120, 32, 84, 42, 70, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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