Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbdcce1ef70c7008b15c0d73e6a35a3c2fd343775df7ae935c5669f62c86a2e

Tx prefix hash: 6e4be610f6d6055dce5458951bd46cf74acf32136f6c2208d990392a36592322
Tx public key: 05ac865595e7644c29fbc28ae31c621ee4baf0b8cb65ca22630437a9280afa5f
Timestamp: 1728050026 Timestamp [UCT]: 2024-10-04 13:53:46 Age [y:d:h:m:s]: 00:108:20:59:38
Block: 1124298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77789 RingCT/type: yes/0
Extra: 0105ac865595e7644c29fbc28ae31c621ee4baf0b8cb65ca22630437a9280afa5f021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19cb4a43e70a90b5cb064254844172b829aa5f73d63b24fc28bbd30ff507dc55 0.600000000000 1606907 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": 1124308, "vin": [ { "gen": { "height": 1124298 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19cb4a43e70a90b5cb064254844172b829aa5f73d63b24fc28bbd30ff507dc55" } } ], "extra": [ 1, 5, 172, 134, 85, 149, 231, 100, 76, 41, 251, 194, 138, 227, 28, 98, 30, 228, 186, 240, 184, 203, 101, 202, 34, 99, 4, 55, 169, 40, 10, 250, 95, 2, 17, 0, 0, 0, 2, 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