Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde39394501545271e6f579f4e19ae48df17fbdf6677df2643c1be515440d5e0

Tx prefix hash: ddc93914bb9f060e47bf5bd6f60809568a8fcd5cee6cb21bca95d33f04940166
Tx public key: ca2986b85b9b7ac68dadd0749366d53ebbf2897b74260e81c9f103cdf3b85989
Timestamp: 1607976112 Timestamp [UCT]: 2020-12-14 20:01:52 Age [y:d:h:m:s]: 04:011:10:14:34
Block: 162100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1020592 RingCT/type: yes/0
Extra: 01ca2986b85b9b7ac68dadd0749366d53ebbf2897b74260e81c9f103cdf3b85989021100000f4f4ea414e5000000000000000000

1 output(s) for total of 178.195234907000 dcy

stealth address amount amount idx
00: 253ae6be3e0a87749da9f7341c71bfb4c051a18b47e5775209a6160d9c818ccb 178.195234907000 288709 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": 162110, "vin": [ { "gen": { "height": 162100 } } ], "vout": [ { "amount": 178195234907, "target": { "key": "253ae6be3e0a87749da9f7341c71bfb4c051a18b47e5775209a6160d9c818ccb" } } ], "extra": [ 1, 202, 41, 134, 184, 91, 155, 122, 198, 141, 173, 208, 116, 147, 102, 213, 62, 187, 242, 137, 123, 116, 38, 14, 129, 201, 241, 3, 205, 243, 184, 89, 137, 2, 17, 0, 0, 15, 79, 78, 164, 20, 229, 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