Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 194493734e0558eb757f078d8c374afcec4abd3e6aeef4a1be73ffaf5c145625

Tx prefix hash: e9bc07a5e65985da4935c66d2044ccf72ca7a1c5a35171b522b489a98f0e766b
Tx public key: b8f242b5014cc9e70a95157423ccb56179ae895a362a3b17a110879a6a96e1b3
Timestamp: 1703466612 Timestamp [UCT]: 2023-12-25 01:10:12 Age [y:d:h:m:s]: 01:106:16:17:46
Block: 920494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337352 RingCT/type: yes/0
Extra: 01b8f242b5014cc9e70a95157423ccb56179ae895a362a3b17a110879a6a96e1b302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ef37f90a3e536a421d2d5a35d1ba7d002632ca210924ffc20cc1d298e2e02be 0.600000000000 1378172 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": 920504, "vin": [ { "gen": { "height": 920494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ef37f90a3e536a421d2d5a35d1ba7d002632ca210924ffc20cc1d298e2e02be" } } ], "extra": [ 1, 184, 242, 66, 181, 1, 76, 201, 231, 10, 149, 21, 116, 35, 204, 181, 97, 121, 174, 137, 90, 54, 42, 59, 23, 161, 16, 135, 154, 106, 150, 225, 179, 2, 17, 0, 0, 0, 1, 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