Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4232ab695a7be625add51143c66beee7b2597a1c80c7dad61499f085f03b034

Tx prefix hash: 8bf5c86a1f8b2065cf2f1b36c29ceba756456ebda2d4e260979400c5f5727652
Tx public key: 9a655190e18b402d99ca0d00ef3e4e0ae526453bd9194b4e1b9180c9b4d98912
Timestamp: 1706171152 Timestamp [UCT]: 2024-01-25 08:25:52 Age [y:d:h:m:s]: 00:356:01:57:21
Block: 942875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254938 RingCT/type: yes/0
Extra: 019a655190e18b402d99ca0d00ef3e4e0ae526453bd9194b4e1b9180c9b4d9891202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1c1dd35eef75173ebb0a30a48d3f64420db67cc6317704754f155a9c93e5d9a 0.600000000000 1401055 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": 942885, "vin": [ { "gen": { "height": 942875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1c1dd35eef75173ebb0a30a48d3f64420db67cc6317704754f155a9c93e5d9a" } } ], "extra": [ 1, 154, 101, 81, 144, 225, 139, 64, 45, 153, 202, 13, 0, 239, 62, 78, 10, 229, 38, 69, 59, 217, 25, 75, 78, 27, 145, 128, 201, 180, 217, 137, 18, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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