Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5159c563599273cd26bbd9f081e189524095b70d6568168f0d4a174e17efc5ad

Tx prefix hash: e74e7056b1e796ffbd0e86ae707f6840cd087a4da312356330ce057b4958afb0
Tx public key: 89c1d78f52458c35fd32ec82f7fbd01cd882356db6d3b249ec52642e22c3da9c
Timestamp: 1723378874 Timestamp [UCT]: 2024-08-11 12:21:14 Age [y:d:h:m:s]: 00:310:12:44:55
Block: 1085571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221742 RingCT/type: yes/0
Extra: 0189c1d78f52458c35fd32ec82f7fbd01cd882356db6d3b249ec52642e22c3da9c021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b6a878d355403a6933795017b4678df22627d1c51f23dd8d3e9dfecfa5cc0a2 0.600000000000 1560158 of 15

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": 1085581, "vin": [ { "gen": { "height": 1085571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b6a878d355403a6933795017b4678df22627d1c51f23dd8d3e9dfecfa5cc0a2" } } ], "extra": [ 1, 137, 193, 215, 143, 82, 69, 140, 53, 253, 50, 236, 130, 247, 251, 208, 28, 216, 130, 53, 109, 182, 211, 178, 73, 236, 82, 100, 46, 34, 195, 218, 156, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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