Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7754069447342b39d4628b7df7c90715b089ae6f7fd00f8df60e89e2dafb3082

Tx prefix hash: 5dd5c416734386e562a189e6644cb239ee4f95fb0bc918505ae8c6458933300f
Tx public key: d1a72e26c7dbfa50fbc7ed760d66f847cfd6e006ee9309d8795228b6fb5b7b55
Timestamp: 1649364245 Timestamp [UCT]: 2022-04-07 20:44:05 Age [y:d:h:m:s]: 02:306:01:05:08
Block: 475359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738280 RingCT/type: yes/0
Extra: 01d1a72e26c7dbfa50fbc7ed760d66f847cfd6e006ee9309d8795228b6fb5b7b5502110000000a4da16a3a000000000000000000

1 output(s) for total of 16.328208738000 dcy

stealth address amount amount idx
00: 0e783d56e1a6eed0c087cb9d74a0e7f2599ebf1cd1656288098cd2985c2324eb 16.328208738000 895592 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": 475369, "vin": [ { "gen": { "height": 475359 } } ], "vout": [ { "amount": 16328208738, "target": { "key": "0e783d56e1a6eed0c087cb9d74a0e7f2599ebf1cd1656288098cd2985c2324eb" } } ], "extra": [ 1, 209, 167, 46, 38, 199, 219, 250, 80, 251, 199, 237, 118, 13, 102, 248, 71, 207, 214, 224, 6, 238, 147, 9, 216, 121, 82, 40, 182, 251, 91, 123, 85, 2, 17, 0, 0, 0, 10, 77, 161, 106, 58, 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