Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1912c1e393d44f10344db4651c93ce8d85cacb9ad7eeabfc478df73cfa67f20

Tx prefix hash: 884318d03c50aeb4732e5e4de754bf470010263eed93b0ed804731d5e19150b1
Tx public key: 53b7b93a64e63a760683b2cf9d44386222d98344ac4e72cb95f266c81e981b9c
Timestamp: 1577792765 Timestamp [UCT]: 2019-12-31 11:46:05 Age [y:d:h:m:s]: 04:324:20:21:03
Block: 35692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121295 RingCT/type: yes/0
Extra: 0153b7b93a64e63a760683b2cf9d44386222d98344ac4e72cb95f266c81e981b9c0211000000028a2ee0d9000000000000000000

1 output(s) for total of 467.453527594000 dcy

stealth address amount amount idx
00: 521e4a047232f87678750a9cb8319196189717d0c5efa0efb0d75bc66d8acd20 467.453527594000 60265 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": 35702, "vin": [ { "gen": { "height": 35692 } } ], "vout": [ { "amount": 467453527594, "target": { "key": "521e4a047232f87678750a9cb8319196189717d0c5efa0efb0d75bc66d8acd20" } } ], "extra": [ 1, 83, 183, 185, 58, 100, 230, 58, 118, 6, 131, 178, 207, 157, 68, 56, 98, 34, 217, 131, 68, 172, 78, 114, 203, 149, 242, 102, 200, 30, 152, 27, 156, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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