Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96ff259011e9b912c4ee1b1a2f9223122650610e5861d505fde55e67cf37252

Tx prefix hash: c7a4d927ee74a3d42dd2166334e6de3056f73242c049e6cc3e63342bb402f99b
Tx public key: 5326cd2d6b95f308ce72291eb6d91db3563dbcb7056a644f1293100be5f08a84
Timestamp: 1579675880 Timestamp [UCT]: 2020-01-22 06:51:20 Age [y:d:h:m:s]: 04:345:19:21:15
Block: 50728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1136830 RingCT/type: yes/0
Extra: 015326cd2d6b95f308ce72291eb6d91db3563dbcb7056a644f1293100be5f08a840211000000034943cd9f000000000000000000

1 output(s) for total of 416.790594328000 dcy

stealth address amount amount idx
00: 543fdf50aa0719af22c6d392bfdc7dde1daa70160c905afbd1d1848bbc9f8c63 416.790594328000 94082 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": 50738, "vin": [ { "gen": { "height": 50728 } } ], "vout": [ { "amount": 416790594328, "target": { "key": "543fdf50aa0719af22c6d392bfdc7dde1daa70160c905afbd1d1848bbc9f8c63" } } ], "extra": [ 1, 83, 38, 205, 45, 107, 149, 243, 8, 206, 114, 41, 30, 182, 217, 29, 179, 86, 61, 188, 183, 5, 106, 100, 79, 18, 147, 16, 11, 229, 240, 138, 132, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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