Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1164704035131f22521236609cadfd29136269b448acd2a8a7eff5573fa481e3

Tx prefix hash: 09c352775aaf865326a8b791c85e9d3c56323bd94a31e35ed7c56e745333d602
Tx public key: e75a6408b74e123b804866b31ceb86d29f7a2ec9956e5b2c2fbfd2c02c65e60d
Timestamp: 1720483621 Timestamp [UCT]: 2024-07-09 00:07:01 Age [y:d:h:m:s]: 00:200:00:21:56
Block: 1061572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143070 RingCT/type: yes/0
Extra: 01e75a6408b74e123b804866b31ceb86d29f7a2ec9956e5b2c2fbfd2c02c65e60d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0deae6149c10a4128b9050b8d4c5cf61cbb5be52090c07b52bef467db63de7f9 0.600000000000 1532063 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": 1061582, "vin": [ { "gen": { "height": 1061572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0deae6149c10a4128b9050b8d4c5cf61cbb5be52090c07b52bef467db63de7f9" } } ], "extra": [ 1, 231, 90, 100, 8, 183, 78, 18, 59, 128, 72, 102, 179, 28, 235, 134, 210, 159, 122, 46, 201, 149, 110, 91, 44, 47, 191, 210, 192, 44, 101, 230, 13, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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