Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aecc5746b7cca43edbf739d52505cdc035ac22dfd992f0d64bc354ad2b684f81

Tx prefix hash: f39a397239df7dd8c9d44e6ac7bbb45ccdc31de2095209da57efd6678158dbff
Tx public key: 29f253446e350da6df39f362d9a7f1958caea7f81a20cb715ed8dcbd88aaa4c2
Timestamp: 1727947441 Timestamp [UCT]: 2024-10-03 09:24:01 Age [y:d:h:m:s]: 00:111:19:37:16
Block: 1123445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79900 RingCT/type: yes/0
Extra: 0129f253446e350da6df39f362d9a7f1958caea7f81a20cb715ed8dcbd88aaa4c2021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19e4262ddf1bf0ebdccd9d0944a2f361eaec07d8b3d6bc7dc801628e09546c6 0.600000000000 1605980 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": 1123455, "vin": [ { "gen": { "height": 1123445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19e4262ddf1bf0ebdccd9d0944a2f361eaec07d8b3d6bc7dc801628e09546c6" } } ], "extra": [ 1, 41, 242, 83, 68, 110, 53, 13, 166, 223, 57, 243, 98, 217, 167, 241, 149, 140, 174, 167, 248, 26, 32, 203, 113, 94, 216, 220, 189, 136, 170, 164, 194, 2, 17, 0, 0, 0, 9, 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