Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9330c65aa4da0ed4540e597ea3873eb4aff2d5cfa53099ea70d52892363c0e86

Tx prefix hash: 7887a53dc17553acc866b1ab900f409df70b8cf33a068938df906b32a98e85c2
Tx public key: 6a40499166738bf320b31ae89a0c1322e3f225f2fea7a9f90694c775c58be8fb
Timestamp: 1580697033 Timestamp [UCT]: 2020-02-03 02:30:33 Age [y:d:h:m:s]: 05:004:21:20:33
Block: 57517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1155455 RingCT/type: yes/0
Extra: 016a40499166738bf320b31ae89a0c1322e3f225f2fea7a9f90694c775c58be8fb02110000000517786bcf000000000000000000

1 output(s) for total of 395.758835655000 dcy

stealth address amount amount idx
00: 64fffa55ac345b6575b22b69a80a3701c9f29801b52e84e5610c24202dd1bf49 395.758835655000 106310 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": 57527, "vin": [ { "gen": { "height": 57517 } } ], "vout": [ { "amount": 395758835655, "target": { "key": "64fffa55ac345b6575b22b69a80a3701c9f29801b52e84e5610c24202dd1bf49" } } ], "extra": [ 1, 106, 64, 73, 145, 102, 115, 139, 243, 32, 179, 26, 232, 154, 12, 19, 34, 227, 242, 37, 242, 254, 167, 169, 249, 6, 148, 199, 117, 197, 139, 232, 251, 2, 17, 0, 0, 0, 5, 23, 120, 107, 207, 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