Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 873851ed1f18859a79c13d553aa1188ed79db7a4d8d2206b60539810a7ca2d84

Tx prefix hash: 790f75b53b1a4c7840ef0d0769fdb034443c35ee1333b283459aad8a235715e9
Tx public key: 22b43eabac72cb745577e5993915377d87d0c2790ea1e93e7b34a72ab45e8d45
Timestamp: 1711925272 Timestamp [UCT]: 2024-03-31 22:47:52 Age [y:d:h:m:s]: 01:010:00:14:37
Block: 990624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268102 RingCT/type: yes/0
Extra: 0122b43eabac72cb745577e5993915377d87d0c2790ea1e93e7b34a72ab45e8d450211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95fafd5440b5edca85fec45fea224d8c3266067e061c8638efbb02d93b5a0064 0.600000000000 1450948 of 15

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": 990634, "vin": [ { "gen": { "height": 990624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95fafd5440b5edca85fec45fea224d8c3266067e061c8638efbb02d93b5a0064" } } ], "extra": [ 1, 34, 180, 62, 171, 172, 114, 203, 116, 85, 119, 229, 153, 57, 21, 55, 125, 135, 208, 194, 121, 14, 161, 233, 62, 123, 52, 167, 42, 180, 94, 141, 69, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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