Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 719b765347dbf283d530d62e0cfda8433b1c18a95314655d42814918a3bb8948

Tx prefix hash: 44e805a28b6a6e97fb80411b008f8a64c0ce490a034294b71f837efd8e31f618
Tx public key: 96444a0eb4ed5f4dd1531fb57f89f9bff85ce6c69f9f6d73c0c50ffc998898ee
Timestamp: 1645861173 Timestamp [UCT]: 2022-02-26 07:39:33 Age [y:d:h:m:s]: 02:276:02:13:11
Block: 446762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 716715 RingCT/type: yes/0
Extra: 0196444a0eb4ed5f4dd1531fb57f89f9bff85ce6c69f9f6d73c0c50ffc998898ee0211000000014a0f5013000000000000000000

1 output(s) for total of 20.311426681000 dcy

stealth address amount amount idx
00: 9aa4a5987069728c300de78ebe42b8aada5de9e181e6a74d900c178099bcf509 20.311426681000 860717 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": 446772, "vin": [ { "gen": { "height": 446762 } } ], "vout": [ { "amount": 20311426681, "target": { "key": "9aa4a5987069728c300de78ebe42b8aada5de9e181e6a74d900c178099bcf509" } } ], "extra": [ 1, 150, 68, 74, 14, 180, 237, 95, 77, 209, 83, 31, 181, 127, 137, 249, 191, 248, 92, 230, 198, 159, 159, 109, 115, 192, 197, 15, 252, 153, 136, 152, 238, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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