Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a31c063b7d8619c71d8ae46e1719af3c8471bbec11c50a9354552d7acae5058

Tx prefix hash: fb81d37f467f237f652bd0dbb57ec9cfbfa10651ef4358b56944ed173d4d6777
Tx public key: 620db05da3c756b65c45f2f9612d8e22ee3c9fd8cce0cfbdd0c7e51f4536b9c2
Timestamp: 1731875672 Timestamp [UCT]: 2024-11-17 20:34:32 Age [y:d:h:m:s]: 00:118:23:54:31
Block: 1155926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84873 RingCT/type: yes/0
Extra: 01620db05da3c756b65c45f2f9612d8e22ee3c9fd8cce0cfbdd0c7e51f4536b9c2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30dc7864cc5c1cd16013cab88f263fe7394236d769e8452fe5a2ab669c6f91dd 0.600000000000 1641545 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": 1155936, "vin": [ { "gen": { "height": 1155926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30dc7864cc5c1cd16013cab88f263fe7394236d769e8452fe5a2ab669c6f91dd" } } ], "extra": [ 1, 98, 13, 176, 93, 163, 199, 86, 182, 92, 69, 242, 249, 97, 45, 142, 34, 238, 60, 159, 216, 204, 224, 207, 189, 208, 199, 229, 31, 69, 54, 185, 194, 2, 17, 0, 0, 0, 2, 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