Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0355ee352d1631deb01722f62e8e61e1fa2ba1269154958418271e9f2c5af987

Tx prefix hash: 44e8a2a47549a3f4b4db53cca13122540b38a7558b4160db479789b1c78f2f38
Tx public key: 871da2fbc0d674529cbb6e48a8f6ba0825e8bc7537b3c4375d1f650fd813ec49
Timestamp: 1707425126 Timestamp [UCT]: 2024-02-08 20:45:26 Age [y:d:h:m:s]: 01:069:22:32:03
Block: 953293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311052 RingCT/type: yes/0
Extra: 01871da2fbc0d674529cbb6e48a8f6ba0825e8bc7537b3c4375d1f650fd813ec4902110000000410a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66ab17828bde532cdd6f24f89c532b3ba63d627e02ee47e0151429b2ea32e50d 0.600000000000 1412485 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": 953303, "vin": [ { "gen": { "height": 953293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66ab17828bde532cdd6f24f89c532b3ba63d627e02ee47e0151429b2ea32e50d" } } ], "extra": [ 1, 135, 29, 162, 251, 192, 214, 116, 82, 156, 187, 110, 72, 168, 246, 186, 8, 37, 232, 188, 117, 55, 179, 196, 55, 93, 31, 101, 15, 216, 19, 236, 73, 2, 17, 0, 0, 0, 4, 16, 161, 116, 143, 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