Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ae99fc641bf25f976de788c5f6f25be60f0345f8f3cf8132505ef0b3cf61b19

Tx prefix hash: 70cb2d6492a142d9f14c1ce799503cb8f0725282db07c369d10f45cab66ca82c
Tx public key: 7d01bf599f91139a6c026b3f32ea1532db1ea4379a1012ca0709b5593c5af26b
Timestamp: 1672515957 Timestamp [UCT]: 2022-12-31 19:45:57 Age [y:d:h:m:s]: 02:097:18:46:09
Block: 664747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 591581 RingCT/type: yes/0
Extra: 017d01bf599f91139a6c026b3f32ea1532db1ea4379a1012ca0709b5593c5af26b021100000002e7ace25d000000000000000000

1 output(s) for total of 3.849614171000 dcy

stealth address amount amount idx
00: 01ba494b076e5a291a5ff0a36eda6eaa1e9a8e96e4f1b9127cb8c0f445e44a0a 3.849614171000 1105752 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": 664757, "vin": [ { "gen": { "height": 664747 } } ], "vout": [ { "amount": 3849614171, "target": { "key": "01ba494b076e5a291a5ff0a36eda6eaa1e9a8e96e4f1b9127cb8c0f445e44a0a" } } ], "extra": [ 1, 125, 1, 191, 89, 159, 145, 19, 154, 108, 2, 107, 63, 50, 234, 21, 50, 219, 30, 164, 55, 154, 16, 18, 202, 7, 9, 181, 89, 60, 90, 242, 107, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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