Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 645d83865852914ed885d2ff8defcb8b705a475dd9c1f315cb43342d7726aeb6

Tx prefix hash: 24e50d73207a4c1ea936a19e236ccf066eafa6a67abde7ecede5845169bb044f
Tx public key: a0b3c75368e7c93e8c711ea1bc1efd6618a902c39c6c1e62a506de442e087c89
Timestamp: 1672709825 Timestamp [UCT]: 2023-01-03 01:37:05 Age [y:d:h:m:s]: 02:092:00:33:27
Block: 666359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587449 RingCT/type: yes/0
Extra: 01a0b3c75368e7c93e8c711ea1bc1efd6618a902c39c6c1e62a506de442e087c8902110000000175e3f0e9000000000000000000

1 output(s) for total of 3.802559136000 dcy

stealth address amount amount idx
00: 860283df6e5e27641f74584f4e2fda53682d367440616fa6a6809cb982ab148b 3.802559136000 1107466 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": 666369, "vin": [ { "gen": { "height": 666359 } } ], "vout": [ { "amount": 3802559136, "target": { "key": "860283df6e5e27641f74584f4e2fda53682d367440616fa6a6809cb982ab148b" } } ], "extra": [ 1, 160, 179, 199, 83, 104, 231, 201, 62, 140, 113, 30, 161, 188, 30, 253, 102, 24, 169, 2, 195, 156, 108, 30, 98, 165, 6, 222, 68, 46, 8, 124, 137, 2, 17, 0, 0, 0, 1, 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