Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94b1b70ad4e629d344630f3ec1bbb80626b79c4bbe2f7e844579773a0d1de840

Tx prefix hash: 842340293f5769eab44be3e6e16ddfd2bb81902f9177714268cc840becddb8ff
Tx public key: c8ca9dd93fb5160e235554937500ac2a0220fb9baadfb50b5dda3b469e9cbf41
Timestamp: 1588736687 Timestamp [UCT]: 2020-05-06 03:44:47 Age [y:d:h:m:s]: 04:294:08:57:10
Block: 98962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126541 RingCT/type: yes/0
Extra: 01c8ca9dd93fb5160e235554937500ac2a0220fb9baadfb50b5dda3b469e9cbf410211000000014ac5aa02000000000000000000

1 output(s) for total of 288.468619613000 dcy

stealth address amount amount idx
00: 159e71313eba4ae2a24c6a360ecda8ae64adc2f3c40f9a1317ede1e8a4cc6fa7 288.468619613000 174782 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": 98972, "vin": [ { "gen": { "height": 98962 } } ], "vout": [ { "amount": 288468619613, "target": { "key": "159e71313eba4ae2a24c6a360ecda8ae64adc2f3c40f9a1317ede1e8a4cc6fa7" } } ], "extra": [ 1, 200, 202, 157, 217, 63, 181, 22, 14, 35, 85, 84, 147, 117, 0, 172, 42, 2, 32, 251, 155, 170, 223, 181, 11, 93, 218, 59, 70, 158, 156, 191, 65, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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