Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc945efbd01f98eab0fa376cb6c42f2e33501112592fd1d71f74430249b627f0

Tx prefix hash: 8518ee393e2150b84a6eee4486d12435d0d3a05655ca25a442bfe8e1e0828bf2
Tx public key: cb13e1713fca6d421423f1b457792fefa9b84e5e374a69d3ca79b1d94532051c
Timestamp: 1733473279 Timestamp [UCT]: 2024-12-06 08:21:19 Age [y:d:h:m:s]: 00:158:01:01:52
Block: 1169149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112785 RingCT/type: yes/0
Extra: 01cb13e1713fca6d421423f1b457792fefa9b84e5e374a69d3ca79b1d94532051c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01252f621930f65d02041c36932772b3c2c48f3fe04f0ba1d51b9351ada40d9b 0.600000000000 1654862 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": 1169159, "vin": [ { "gen": { "height": 1169149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01252f621930f65d02041c36932772b3c2c48f3fe04f0ba1d51b9351ada40d9b" } } ], "extra": [ 1, 203, 19, 225, 113, 63, 202, 109, 66, 20, 35, 241, 180, 87, 121, 47, 239, 169, 184, 78, 94, 55, 74, 105, 211, 202, 121, 177, 217, 69, 50, 5, 28, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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