Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38ecf1a7cf70ef1ac2342aef9d56fbbd948391475298cb0acf6cea37eed3732a

Tx prefix hash: db263d6e22133cccee0fd9d2d7cdd6cd0bbb95057e4f93c9865a83b729838ec6
Tx public key: 1e21a877a98af9b8a03edf344ffb64b70e907c72d2286af2a6b568fb357f56a8
Timestamp: 1700895733 Timestamp [UCT]: 2023-11-25 07:02:13 Age [y:d:h:m:s]: 01:055:11:36:54
Block: 899163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301021 RingCT/type: yes/0
Extra: 011e21a877a98af9b8a03edf344ffb64b70e907c72d2286af2a6b568fb357f56a802110000000375e3f0e9000000000000000000

1 output(s) for total of 0.643724006000 dcy

stealth address amount amount idx
00: bb9cc0778e6c614dec87b3c428bfaaa9f05d3df36d116916a0ecd3a83c22607e 0.643724006000 1355606 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": 899173, "vin": [ { "gen": { "height": 899163 } } ], "vout": [ { "amount": 643724006, "target": { "key": "bb9cc0778e6c614dec87b3c428bfaaa9f05d3df36d116916a0ecd3a83c22607e" } } ], "extra": [ 1, 30, 33, 168, 119, 169, 138, 249, 184, 160, 62, 223, 52, 79, 251, 100, 183, 14, 144, 124, 114, 210, 40, 106, 242, 166, 181, 104, 251, 53, 127, 86, 168, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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