Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a9b47d9dc263e71df7472ba71c1b8b1a8144a0076db86cff1dcaaf126691ac7

Tx prefix hash: ca6bdb4eef67c06d7b26a6b68f8a84101a6a5a5f30f5344f79fdc9dcaa224437
Tx public key: 39a031d4b3f36eb50466f8a4e80f4bd6c21c824ec182924ec82de5a50d0c7066
Timestamp: 1693790021 Timestamp [UCT]: 2023-09-04 01:13:41 Age [y:d:h:m:s]: 01:178:04:52:33
Block: 840438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388456 RingCT/type: yes/0
Extra: 0139a031d4b3f36eb50466f8a4e80f4bd6c21c824ec182924ec82de5a50d0c706602110000000533af99f4000000000000000000

1 output(s) for total of 1.007611290000 dcy

stealth address amount amount idx
00: cf16a9465a954fb9b0b899304aeeb6293206672ade0addaf459c9330fec8a42b 1.007611290000 1293376 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": 840448, "vin": [ { "gen": { "height": 840438 } } ], "vout": [ { "amount": 1007611290, "target": { "key": "cf16a9465a954fb9b0b899304aeeb6293206672ade0addaf459c9330fec8a42b" } } ], "extra": [ 1, 57, 160, 49, 212, 179, 243, 110, 181, 4, 102, 248, 164, 232, 15, 75, 214, 194, 28, 130, 78, 193, 130, 146, 78, 200, 45, 229, 165, 13, 12, 112, 102, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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