Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b480ff078aae0063bf2c85f7dc34968a761beca88140e41a4549f3cc4a12951f

Tx prefix hash: e11b8fcd3b4d9d8574bf992bcc0b54fc5bd6dcf9da7e92a5c793975e44bb3cdb
Tx public key: d5b9cb0c75eeb5686348d05906b7406aa043969023aa380da3c5134ab84ee805
Timestamp: 1712854870 Timestamp [UCT]: 2024-04-11 17:01:10 Age [y:d:h:m:s]: 01:006:23:12:06
Block: 998293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265959 RingCT/type: yes/0
Extra: 01d5b9cb0c75eeb5686348d05906b7406aa043969023aa380da3c5134ab84ee8050211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 272177418b61d8b9c977cbc19272eda2a82dea07fbcdb313aa0c1f523a7b75db 0.600000000000 1458739 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": 998303, "vin": [ { "gen": { "height": 998293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "272177418b61d8b9c977cbc19272eda2a82dea07fbcdb313aa0c1f523a7b75db" } } ], "extra": [ 1, 213, 185, 203, 12, 117, 238, 181, 104, 99, 72, 208, 89, 6, 183, 64, 106, 160, 67, 150, 144, 35, 170, 56, 13, 163, 197, 19, 74, 184, 78, 232, 5, 2, 17, 0, 0, 0, 5, 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