Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fb2ab42660eaafcb3ee7dd38ee9e68b534d6e85549fb1a9eb293ed595d6f1af

Tx prefix hash: f227f2ff118a66aea71e2f60913c7ef8ef801f18cce300129012c9ee287084b9
Tx public key: 4ea912edf19bd94044ce50c64c4fb562b5906186aa60b3a9be0a3dafa202a06d
Timestamp: 1726999107 Timestamp [UCT]: 2024-09-22 09:58:27 Age [y:d:h:m:s]: 00:109:22:53:37
Block: 1115583 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78618 RingCT/type: yes/0
Extra: 014ea912edf19bd94044ce50c64c4fb562b5906186aa60b3a9be0a3dafa202a06d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dec841c1e2abe3d369c66753b3f47937cc8bea6e1c0f3c39a3f7dbb992e15fb9 0.600000000000 1595768 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": 1115593, "vin": [ { "gen": { "height": 1115583 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dec841c1e2abe3d369c66753b3f47937cc8bea6e1c0f3c39a3f7dbb992e15fb9" } } ], "extra": [ 1, 78, 169, 18, 237, 241, 155, 217, 64, 68, 206, 80, 198, 76, 79, 181, 98, 181, 144, 97, 134, 170, 96, 179, 169, 190, 10, 61, 175, 162, 2, 160, 109, 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