Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf1dd35a975d0019d174882c29127f8598d9841d1554824f22dde218e7db787

Tx prefix hash: 09a413b10e75be8e2a175b4c55927b742ccfc90b6dfe1e7fbccde047378079f0
Tx public key: 509abbda45edfd601646a4523965d74498a3e9e2f72dc57baaa63f64caa76f8e
Timestamp: 1697465692 Timestamp [UCT]: 2023-10-16 14:14:52 Age [y:d:h:m:s]: 01:157:11:01:31
Block: 870940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373556 RingCT/type: yes/0
Extra: 01509abbda45edfd601646a4523965d74498a3e9e2f72dc57baaa63f64caa76f8e0211000000014b8f5122000000000000000000

1 output(s) for total of 0.798388479000 dcy

stealth address amount amount idx
00: 865094f90adcbc36f0b0f0ed1f736f909e157ac0a0e39bb0d7eabb3725094d1a 0.798388479000 1325901 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": 870950, "vin": [ { "gen": { "height": 870940 } } ], "vout": [ { "amount": 798388479, "target": { "key": "865094f90adcbc36f0b0f0ed1f736f909e157ac0a0e39bb0d7eabb3725094d1a" } } ], "extra": [ 1, 80, 154, 187, 218, 69, 237, 253, 96, 22, 70, 164, 82, 57, 101, 215, 68, 152, 163, 233, 226, 247, 45, 197, 123, 170, 166, 63, 100, 202, 167, 111, 142, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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