Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23f62ebb319da1e5d0f1804284f72c29b0f20c8a45533e8ce9438d6bc2dfc5d0

Tx prefix hash: 1e95d953f8cbb6012a327c8ad2f4d057fb3f29ae9af7c37510fa3ad91fb667f6
Tx public key: e528bab31037b479efac5d38907f5520f082aab436c0cf8b74d49d57eeafce8a
Timestamp: 1577165790 Timestamp [UCT]: 2019-12-24 05:36:30 Age [y:d:h:m:s]: 05:317:00:51:56
Block: 30402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1374205 RingCT/type: yes/0
Extra: 01e528bab31037b479efac5d38907f5520f082aab436c0cf8b74d49d57eeafce8a021100000017e39b962a000000000000000000

1 output(s) for total of 486.705680680000 dcy

stealth address amount amount idx
00: c9f324f5458dfb9cfc51f3d8f0dcb3619e532e0dc212ebdbf24d06e01babdeee 486.705680680000 50206 of 0

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": 30412, "vin": [ { "gen": { "height": 30402 } } ], "vout": [ { "amount": 486705680680, "target": { "key": "c9f324f5458dfb9cfc51f3d8f0dcb3619e532e0dc212ebdbf24d06e01babdeee" } } ], "extra": [ 1, 229, 40, 186, 179, 16, 55, 180, 121, 239, 172, 93, 56, 144, 127, 85, 32, 240, 130, 170, 180, 54, 192, 207, 139, 116, 212, 157, 87, 238, 175, 206, 138, 2, 17, 0, 0, 0, 23, 227, 155, 150, 42, 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