Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 962d5ecd60a0787f096ef6776a6adf79f1da56136f58e524e55476a7201e1253

Tx prefix hash: 6417bed34bc2e6d13745fb8d8c327b0cfe5b6aae8d7efe741c9e544f14ef77cf
Tx public key: 9c80402589e4ac24cc709a846e62f809dc10e61b35e0262db686b288836cf19c
Timestamp: 1636584243 Timestamp [UCT]: 2021-11-10 22:44:03 Age [y:d:h:m:s]: 03:053:19:11:50
Block: 371688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 817062 RingCT/type: yes/0
Extra: 019c80402589e4ac24cc709a846e62f809dc10e61b35e0262db686b288836cf19c02110000001b328bb496000000000000000000

1 output(s) for total of 36.011710717000 dcy

stealth address amount amount idx
00: 599b473aacd6e1f314049971502ece8d7ab349761c406ed8733b77604e4fbeb1 36.011710717000 753142 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": 371698, "vin": [ { "gen": { "height": 371688 } } ], "vout": [ { "amount": 36011710717, "target": { "key": "599b473aacd6e1f314049971502ece8d7ab349761c406ed8733b77604e4fbeb1" } } ], "extra": [ 1, 156, 128, 64, 37, 137, 228, 172, 36, 204, 112, 154, 132, 110, 98, 248, 9, 220, 16, 230, 27, 53, 224, 38, 45, 182, 134, 178, 136, 131, 108, 241, 156, 2, 17, 0, 0, 0, 27, 50, 139, 180, 150, 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