Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 285ba49ba7dd8265f1fe08e3ab89b7f285fae7ad91308439fa0a086179efeeaa

Tx prefix hash: 720e55d83d6052789f9d127e9e2e6058b7dc2df61d5b6410374c3f7d90b751b0
Tx public key: 54f85a3f4afb5a8a67c2a1d72896a34e555b973388db42e524ebda2b845e08f3
Timestamp: 1706505837 Timestamp [UCT]: 2024-01-29 05:23:57 Age [y:d:h:m:s]: 01:069:10:32:33
Block: 945660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310707 RingCT/type: yes/0
Extra: 0154f85a3f4afb5a8a67c2a1d72896a34e555b973388db42e524ebda2b845e08f30211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec6f55e8e36a2fba28777b81c46a9d7a5c2d27d249447cee9fda61b5ba7af6a5 0.600000000000 1403976 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": 945670, "vin": [ { "gen": { "height": 945660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec6f55e8e36a2fba28777b81c46a9d7a5c2d27d249447cee9fda61b5ba7af6a5" } } ], "extra": [ 1, 84, 248, 90, 63, 74, 251, 90, 138, 103, 194, 161, 215, 40, 150, 163, 78, 85, 91, 151, 51, 136, 219, 66, 229, 36, 235, 218, 43, 132, 94, 8, 243, 2, 17, 0, 0, 0, 4, 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