Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77e40b476030ce0fdbcaf1e8d2c03fe3deab4d9bd43b920fbf7d958f1f4bbcbf

Tx prefix hash: 2c80caa61e979f30c384822d5f20bf0acc3497767d7659acc4688438234fec48
Tx public key: 801b26242aa5703e6fde023fa0bda18c291610a04db5abf8f75899133f1cb9b3
Timestamp: 1583454261 Timestamp [UCT]: 2020-03-06 00:24:21 Age [y:d:h:m:s]: 04:316:02:23:57
Block: 77092 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1120507 RingCT/type: yes/0
Extra: 01801b26242aa5703e6fde023fa0bda18c291610a04db5abf8f75899133f1cb9b30211000000128a2ee0d9000000000000000000

1 output(s) for total of 340.849762557000 dcy

stealth address amount amount idx
00: c1ea6f65e24d16c342c4e650a281c99f17ae6a0a839317ef6e25449b59ff53b5 340.849762557000 141936 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": 77102, "vin": [ { "gen": { "height": 77092 } } ], "vout": [ { "amount": 340849762557, "target": { "key": "c1ea6f65e24d16c342c4e650a281c99f17ae6a0a839317ef6e25449b59ff53b5" } } ], "extra": [ 1, 128, 27, 38, 36, 42, 165, 112, 62, 111, 222, 2, 63, 160, 189, 161, 140, 41, 22, 16, 160, 77, 181, 171, 248, 247, 88, 153, 19, 63, 28, 185, 179, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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