Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecdb9c32a128b9263f05d9f23656109120f15f3804be184617895250bc13ec9c

Tx prefix hash: 91bb6378c07969fbefab37bc9b5f0281b6b73314ae125b23c221242a151e17a0
Tx public key: 5ae1af20a635808660efedacb48e9e0e5b98f11b793d698a9bbf4f71e311dcf3
Timestamp: 1724437644 Timestamp [UCT]: 2024-08-23 18:27:24 Age [y:d:h:m:s]: 00:226:03:53:52
Block: 1094362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161470 RingCT/type: yes/0
Extra: 015ae1af20a635808660efedacb48e9e0e5b98f11b793d698a9bbf4f71e311dcf3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 084043b1b613663d8c9c76ce2502d44a6a10e8f4983d06eb08d17165c05d9064 0.600000000000 1569479 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": 1094372, "vin": [ { "gen": { "height": 1094362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "084043b1b613663d8c9c76ce2502d44a6a10e8f4983d06eb08d17165c05d9064" } } ], "extra": [ 1, 90, 225, 175, 32, 166, 53, 128, 134, 96, 239, 237, 172, 180, 142, 158, 14, 91, 152, 241, 27, 121, 61, 105, 138, 155, 191, 79, 113, 227, 17, 220, 243, 2, 17, 0, 0, 0, 4, 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