Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c113afe91b8c53c62f62f2e18f3b0fb7b2d78277bd66515ded82472dc03cfaa

Tx prefix hash: 8fb98bd4420738d0913108bc642120ca9906c2f623be6ef3ecf6e3e429b39f45
Tx public key: f7be1752b6a2248f6ede54ec8330cfeb44409262c4dee5f29647af7e3f4108d5
Timestamp: 1696958292 Timestamp [UCT]: 2023-10-10 17:18:12 Age [y:d:h:m:s]: 01:219:14:16:52
Block: 866740 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418001 RingCT/type: yes/0
Extra: 01f7be1752b6a2248f6ede54ec8330cfeb44409262c4dee5f29647af7e3f4108d502110000000c75e3f0e9000000000000000000

1 output(s) for total of 0.824386006000 dcy

stealth address amount amount idx
00: 23657869e4d60683473883e8b5417ee1d2933c89bf0dd8095cfc7e9d92041d42 0.824386006000 1321370 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": 866750, "vin": [ { "gen": { "height": 866740 } } ], "vout": [ { "amount": 824386006, "target": { "key": "23657869e4d60683473883e8b5417ee1d2933c89bf0dd8095cfc7e9d92041d42" } } ], "extra": [ 1, 247, 190, 23, 82, 182, 162, 36, 143, 110, 222, 84, 236, 131, 48, 207, 235, 68, 64, 146, 98, 196, 222, 229, 242, 150, 71, 175, 126, 63, 65, 8, 213, 2, 17, 0, 0, 0, 12, 117, 227, 240, 233, 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