Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ed137a400243debf4e8f22b7a7d34df936ff99e42595958348fac935caed14

Tx prefix hash: e8fcbd937a59585f813373ec858b702d23ae4aa2ed6486bfaac6eec1c09b5c83
Tx public key: 0fb32eee7219679f9d8a49c9bfa0dc17e3ee39d142b4e775af23a009288552f7
Timestamp: 1723775455 Timestamp [UCT]: 2024-08-16 02:30:55 Age [y:d:h:m:s]: 01:141:03:11:57
Block: 1088864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359402 RingCT/type: yes/0
Extra: 010fb32eee7219679f9d8a49c9bfa0dc17e3ee39d142b4e775af23a009288552f702110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da0056357a57e0e35fd6a5f4881def8b4d815042a5d737a8b105955038cce94e 0.600000000000 1563483 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": 1088874, "vin": [ { "gen": { "height": 1088864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da0056357a57e0e35fd6a5f4881def8b4d815042a5d737a8b105955038cce94e" } } ], "extra": [ 1, 15, 179, 46, 238, 114, 25, 103, 159, 157, 138, 73, 201, 191, 160, 220, 23, 227, 238, 57, 209, 66, 180, 231, 117, 175, 35, 160, 9, 40, 133, 82, 247, 2, 17, 0, 0, 0, 13, 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