Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9054e80b89bb477bacb49e7b0d10c85c7e1056945257e7330544cf960a6223f

Tx prefix hash: cde825c827be93ec5e8f673e674c6ad41f4351e5d25bf7afa1430caecd4d684c
Tx public key: 985adce0c9338d9425e84d6da69bc91534d7656591ce7438c2fea9f8b561c48e
Timestamp: 1628707620 Timestamp [UCT]: 2021-08-11 18:47:00 Age [y:d:h:m:s]: 03:272:03:35:30
Block: 311945 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 967505 RingCT/type: yes/0
Extra: 01985adce0c9338d9425e84d6da69bc91534d7656591ce7438c2fea9f8b561c48e02110000002a01f1e57f000000000000000000

1 output(s) for total of 56.807370310000 dcy

stealth address amount amount idx
00: 22a9812677fbd4104f6b06e504b4c28f2c5e838425053e730e83da18b58c540a 56.807370310000 649124 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": 311955, "vin": [ { "gen": { "height": 311945 } } ], "vout": [ { "amount": 56807370310, "target": { "key": "22a9812677fbd4104f6b06e504b4c28f2c5e838425053e730e83da18b58c540a" } } ], "extra": [ 1, 152, 90, 220, 224, 201, 51, 141, 148, 37, 232, 77, 109, 166, 155, 201, 21, 52, 215, 101, 101, 145, 206, 116, 56, 194, 254, 169, 248, 181, 97, 196, 142, 2, 17, 0, 0, 0, 42, 1, 241, 229, 127, 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