Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab8d46e8db1c9524ef4ab3bb3ae253c90277ebb9293f6955777a2efbab010888

Tx prefix hash: e83f2fed1aaa97a8c674eb95b32695720e0ce8d203bff513d09069b5aca32ecc
Tx public key: 6c5a3cdfa2915629ee8e9a2a407ec719d969d1a66f4d1baafa8688ccb6c1ab6f
Timestamp: 1728312824 Timestamp [UCT]: 2024-10-07 14:53:44 Age [y:d:h:m:s]: 00:166:19:05:13
Block: 1126473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119003 RingCT/type: yes/0
Extra: 016c5a3cdfa2915629ee8e9a2a407ec719d969d1a66f4d1baafa8688ccb6c1ab6f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44d5af959c37e2734a88ec5b592345f4ef3f2e97aba802383835521d68c0f66e 0.600000000000 1609266 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": 1126483, "vin": [ { "gen": { "height": 1126473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44d5af959c37e2734a88ec5b592345f4ef3f2e97aba802383835521d68c0f66e" } } ], "extra": [ 1, 108, 90, 60, 223, 162, 145, 86, 41, 238, 142, 154, 42, 64, 126, 199, 25, 217, 105, 209, 166, 111, 77, 27, 170, 250, 134, 136, 204, 182, 193, 171, 111, 2, 17, 0, 0, 0, 3, 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