Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79265cd302ad10ec547225b65a358441f4394e2a8306ad908b3e96dc14428a40

Tx prefix hash: 32ef1552c37b66beb37d37be5a97e54ead80d7d10f1ce546033d7aea8a0ad2d5
Tx public key: 8d34892116c50b451d63b4d151d0f4a6cf62b6d557969f834e7fb5dad98828f6
Timestamp: 1736370306 Timestamp [UCT]: 2025-01-08 21:05:06 Age [y:d:h:m:s]: 00:074:05:06:40
Block: 1193130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52811 RingCT/type: yes/0
Extra: 018d34892116c50b451d63b4d151d0f4a6cf62b6d557969f834e7fb5dad98828f6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1bde592b75a528d3bc41dc496849a33efe41f9995228ff5deab4c55d7a699d6 0.600000000000 1679689 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": 1193140, "vin": [ { "gen": { "height": 1193130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1bde592b75a528d3bc41dc496849a33efe41f9995228ff5deab4c55d7a699d6" } } ], "extra": [ 1, 141, 52, 137, 33, 22, 197, 11, 69, 29, 99, 180, 209, 81, 208, 244, 166, 207, 98, 182, 213, 87, 150, 159, 131, 78, 127, 181, 218, 217, 136, 40, 246, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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