Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd3e1f4c70a4792d1d414ef360cd786a1af231fa434d37cbda7f7e3dcb318275

Tx prefix hash: cb43fe9889a74d68d1b8a55b14e6b4302360cff75c216a0a8e6b4165fff5fa6d
Tx public key: 1bddca752302d23ec340a1a0d12313f72434a1931f0e012e79de1035a44cef99
Timestamp: 1708675029 Timestamp [UCT]: 2024-02-23 07:57:09 Age [y:d:h:m:s]: 01:041:03:32:26
Block: 963666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290427 RingCT/type: yes/0
Extra: 011bddca752302d23ec340a1a0d12313f72434a1931f0e012e79de1035a44cef990211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f38f378f02fc675f1f69ce7396a4ff79664206eaed4280ea3592a2b08e5a9188 0.600000000000 1423383 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": 963676, "vin": [ { "gen": { "height": 963666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f38f378f02fc675f1f69ce7396a4ff79664206eaed4280ea3592a2b08e5a9188" } } ], "extra": [ 1, 27, 221, 202, 117, 35, 2, 210, 62, 195, 64, 161, 160, 209, 35, 19, 247, 36, 52, 161, 147, 31, 14, 1, 46, 121, 222, 16, 53, 164, 76, 239, 153, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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