Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c69b3d43603f8a55806b05578f7a24289cb0a47b31703dbe3ea2f2ac20f21f8

Tx prefix hash: 0157c6f14b96c5e5d2d22672d122e1dc2fd95ead829d201647099d2082ab1cfb
Tx public key: 9b460f7e14fb79ab9e827cea40eb8eb8ecd2823a4c496fa87d9f1154f54a8798
Timestamp: 1700318744 Timestamp [UCT]: 2023-11-18 14:45:44 Age [y:d:h:m:s]: 01:201:18:53:42
Block: 894391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405437 RingCT/type: yes/0
Extra: 019b460f7e14fb79ab9e827cea40eb8eb8ecd2823a4c496fa87d9f1154f54a879802110000000275e3f0e9000000000000000000

1 output(s) for total of 0.667592316000 dcy

stealth address amount amount idx
00: 9a8c760c74b8e57532e58f3fcc3a9e3eef434afc076eddc1e9e38101539674e7 0.667592316000 1350590 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": 894401, "vin": [ { "gen": { "height": 894391 } } ], "vout": [ { "amount": 667592316, "target": { "key": "9a8c760c74b8e57532e58f3fcc3a9e3eef434afc076eddc1e9e38101539674e7" } } ], "extra": [ 1, 155, 70, 15, 126, 20, 251, 121, 171, 158, 130, 124, 234, 64, 235, 142, 184, 236, 210, 130, 58, 76, 73, 111, 168, 125, 159, 17, 84, 245, 74, 135, 152, 2, 17, 0, 0, 0, 2, 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