Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31a66fec0eeafe43c4046ae357d103ae5d4af96b83be11f6de0073aeba82d24f

Tx prefix hash: 19476b7001a59afaea6c6141a363691dc1fbc946750c0aabcd4073c155029ff5
Tx public key: d3f6df61498cee04e75dca6f10b0fba3a91b0518b25145ef21684a124ad68911
Timestamp: 1701001261 Timestamp [UCT]: 2023-11-26 12:21:01 Age [y:d:h:m:s]: 01:169:18:38:18
Block: 900039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382541 RingCT/type: yes/0
Extra: 01d3f6df61498cee04e75dca6f10b0fba3a91b0518b25145ef21684a124ad68911021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.639436102000 dcy

stealth address amount amount idx
00: a5949b5560f57bd15f999142bd08d4e4454a3c5ba413cb55c341a6fb60be15a8 0.639436102000 1356516 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": 900049, "vin": [ { "gen": { "height": 900039 } } ], "vout": [ { "amount": 639436102, "target": { "key": "a5949b5560f57bd15f999142bd08d4e4454a3c5ba413cb55c341a6fb60be15a8" } } ], "extra": [ 1, 211, 246, 223, 97, 73, 140, 238, 4, 231, 93, 202, 111, 16, 176, 251, 163, 169, 27, 5, 24, 178, 81, 69, 239, 33, 104, 74, 18, 74, 214, 137, 17, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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